[Integrations](https://spiral.ai/integrations) › [Instinct](https://spiral.ai/integrations/instinct) › [GitHub repository issues](https://spiral.ai/integrations/instinct/github-repository-issues)

# How to Use GitHub repository issues in Instinct

Fetch issue reports with titles, descriptions, labels, states, and activity dates. Use them to investigate reported problems or read the evidence behind a backlog count.

|  |  |
| --- | --- |
| Model | GitHub repository issues |
| Available through | Alexandria |
| Category | E-commerce |
| Price | $0.00873 per call. |
| Returns | json |
| Runs | In the background |
| Setup | About 2 minutes, with a Spiral API key |

## Prompts to try with GitHub repository issues in Instinct

- Every Monday at 9am: use GitHub repository issues to look this up and give me the result as a table.
- Pull the latest numbers from GitHub repository issues and tell me what changed since last week.
- Check GitHub repository issues and summarize what you find in three bullet points.
- Pull the newest data from GitHub repository issues and give me the result as a table.
- Check GitHub repository issues every morning and tell me only when something changed.

## How to set up GitHub repository issues in Instinct

Pick the way that suits you. Each takes about two minutes.

### Use the Spiral skill

1. **Send Instinct this message**: Your agent reads Spiral's skill and sets itself up.

```
set up https://spiral.ai/SKILL.md
```

2. **Sign in or paste a key**: Approve Spiral in the browser, or give the agent a key from the console.

### Use Spiral's MCP server

1. **Create an API key**: In the console, open API keys and create a key for Instinct. Copy it.

2. **Send Instinct this message**: Instinct reads Spiral's skill and asks for your API key.

```text
set up https://spiral.ai/SKILL.md
```

3. **Give Instinct the key**: When Instinct asks for the key, add it where Instinct keeps secrets, never in the chat itself.

### Use the Spiral CLI

1. **Install and sign in**: Installs the Spiral CLI, signs you in and adds its skill to your coding agents.

```bash
npx -y spiral-cli@latest init
```

### Call the Spiral API

1. **Create an API key**: In the console, under API keys.

2. **Run GitHub repository issues**: One request; the result comes back by polling or a webhook.

```bash
curl https://api.spiral.ai/v1/runs \
  -H "Authorization: Bearer $SPIRAL_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: $(uuidgen)" \
  -d '{
    "provider": "alexandria",
    "model": "github-com/repositories/issues",
    "input": {
      "repo": "<repo>"
    }
  }'
```

Then paste one of the prompts above: Instinct finds GitHub repository issues on Spiral, shows the price and runs it.

Setup guide in the docs: https://spiral.ai/docs/quickstarts/instinct

## GitHub repository issues tools and prices

- [GitHub · Issues](https://spiral.ai/tools/alexandria/github-com/repositories/issues) (Alexandria): $0.00873 per call.

## Settings you can ask for

| Setting | Allowed values | Default | Description |
| --- | --- | --- | --- |
| url |  | — | HTTPS github.com/{owner}/{name} URL; deeper paths (issues, tree, ...) are accepted and reduced to the repository. Provide exactly one of repo or url. Pattern: ^(?:https?://)?(?:www\.)?github\.com/[A-Za-z0-9-]{1,39}/[A-Za-z0-9._-]{1,100}(?:[/?#].*)?$. |
| page | 1 to 1000 | 1 | 1-based page; has_next in the response says whether page+1 exists. |
| repo |  | — | Repository as `owner/name`, for example `firecrawl/firecrawl`. Provide exactly one of repo or url. Pattern: ^@?/?[A-Za-z0-9](?:[A-Za-z0-9-]{0,37}[A-Za-z0-9])?/[A-Za-z0-9._-]{1,100}(?:\.git)?/?$. |
| sort | created, updated, comments | created | sort |
| state | open, closed, all | open | Issue state to match. |
| labels |  | — | Label names an issue must all carry (AND). Case-insensitive on GitHub's side. |

## What can you do with GitHub repository issues in Instinct?

Produce a recurring change report for selected public projects and packages on GitHub. A scheduled agent can compare saved observations of releases, repository status, issue totals, files, or advisories and report what changed.

### Review a dependency before adoption

Build an adoption brief covering repository status, contribution concentration, license text, issue categories and totals, release history, and reported vulnerability or malware concerns for the exact packages under consideration.

### Prepare a dependency upgrade review

Compare the installed version with published releases, read migration files and known issue reports, and check relevant advisories. Include project status and contribution concentration when deciding how much upstream support to expect.

### Investigate a reported package incident

Read the advisory and affected package ranges, compare release notes and manifests, then inspect related issue categories, reports, and totals. Keep a documented vulnerability fix separate from a malicious-package report.

### Assess upstream maintenance

Compare archive status, contribution concentration, release dates, issue categories, and backlog totals across candidate repositories. Read representative issue reports to explain the numbers.

### Plan an open source contribution

Read contribution instructions, discover the repository's actual labels, and inspect suitable issues alongside backlog totals. Use project status and contribution distribution to understand the project's context before proposing work.

### Compare migration destinations

Compare two public projects using their README files, repository metadata, contribution distribution, release notes, and issue evidence. Summarize which documented limitations matter for the planned migration.

## Overview

- [Alexandria](https://spiral.ai/providers/alexandria)
- [All Instinct guides](https://spiral.ai/integrations/instinct)

## GitHub repository issues in other agents

- [Amp](https://spiral.ai/integrations/amp/github-repository-issues)
- [ChatGPT](https://spiral.ai/integrations/chatgpt/github-repository-issues)
- [Claude](https://spiral.ai/integrations/claude-desktop/github-repository-issues)
- [Claude Code](https://spiral.ai/integrations/claude-code/github-repository-issues)
- [Cline](https://spiral.ai/integrations/cline/github-repository-issues)
- [Codex](https://spiral.ai/integrations/codex/github-repository-issues)
- [Cursor](https://spiral.ai/integrations/cursor/github-repository-issues)
- [Devin](https://spiral.ai/integrations/devin/github-repository-issues)
- [dots](https://spiral.ai/integrations/dots/github-repository-issues)
- [Factory Droid](https://spiral.ai/integrations/factory-droid/github-repository-issues)
- [Gemini](https://spiral.ai/integrations/gemini/github-repository-issues)
- [Gemini CLI](https://spiral.ai/integrations/gemini-cli/github-repository-issues)
- [Google Antigravity](https://spiral.ai/integrations/antigravity/github-repository-issues)
- [goose](https://spiral.ai/integrations/goose/github-repository-issues)
- [Grok](https://spiral.ai/integrations/grok/github-repository-issues)
- [Grok Build](https://spiral.ai/integrations/grok-build/github-repository-issues)
- [Hermes](https://spiral.ai/integrations/hermes/github-repository-issues)
- [Manus](https://spiral.ai/integrations/manus/github-repository-issues)
- [Muse](https://spiral.ai/integrations/muse/github-repository-issues)
- [Muse Code](https://spiral.ai/integrations/muse-code/github-repository-issues)
- [n8n](https://spiral.ai/integrations/n8n/github-repository-issues)
- [Notion](https://spiral.ai/integrations/notion/github-repository-issues)
- [OpenClaw](https://spiral.ai/integrations/openclaw/github-repository-issues)
- [opencode](https://spiral.ai/integrations/opencode/github-repository-issues)
- [Perplexity](https://spiral.ai/integrations/perplexity/github-repository-issues)
- [Raycast](https://spiral.ai/integrations/raycast/github-repository-issues)
- [VS Code](https://spiral.ai/integrations/vscode/github-repository-issues)
- [Windsurf](https://spiral.ai/integrations/windsurf/github-repository-issues)
- [Zapier](https://spiral.ai/integrations/zapier/github-repository-issues)

## More Instinct guides

- [GitHub repository issue counts](https://spiral.ai/integrations/instinct/github-repository-issue-counts)
- [GitHub repository labels](https://spiral.ai/integrations/instinct/github-repository-labels)
- [GitHub repository file](https://spiral.ai/integrations/instinct/github-repository-file)
- [GitHub repository search](https://spiral.ai/integrations/instinct/github-repository-search)
- [GitHub repository details](https://spiral.ai/integrations/instinct/github-repository-details)
- [GitHub repository security advisories](https://spiral.ai/integrations/instinct/github-repository-security-advisories)

## Questions about GitHub repository issues in Instinct

**Can Instinct use GitHub repository issues?**

Yes. Add Spiral to Instinct as an MCP server, and Instinct can find and run GitHub repository issues like any built-in tool.

**How much does GitHub repository issues cost in Instinct?**

$0.00873 per call. You pay from your Spiral balance as you go, with no subscription, and a failed run is not charged. Your Instinct plan is separate.

**Do I need an Alexandria account to use GitHub repository issues in Instinct?**

You need no Alexandria account. Instinct uses one Spiral API key for every tool, and Spiral runs GitHub repository issues on its own Alexandria account.

**How long does it take to set up GitHub repository issues in Instinct?**

About two minutes: create an API key, then send Instinct this message, then give Instinct the key.

**Does Instinct wait while GitHub repository issues runs?**

GitHub repository issues runs in the background. Instinct starts the run, checks on it and gives you the json when it's ready.

**Can I reuse anything that is public on GitHub?**

Public visibility alone does not grant unrestricted reuse. GitHub says that without a license, default copyright restrictions apply to source code; its Advisory Database has a separate CC BY 4.0 license.

**How current is GitHub's data?**

Freshness depends on the record. Contributor results can be a few hours old because GitHub caches them, while a file selected by branch can change whenever new commits arrive.

**Does a GitHub release history include every version tag?**

No. GitHub excludes Git tags that have no associated release, and its latest-release lookup excludes prereleases and drafts.

**Do GitHub issues include pull requests?**

GitHub's underlying issue responses can contain both, with pull requests identified separately. An issue-only backlog should exclude pull requests before its totals are compared.

**Where do GitHub's malware reports come from?**

GitHub automatically publishes malware advisories from the npm security team and the OpenSSF Malicious Packages repository. These reports concern malicious packages and are separate from ordinary vulnerability advisories.

