[Integrations](https://spiral.ai/integrations) › [Muse](https://spiral.ai/integrations/muse) › [GitHub repository issue counts](https://spiral.ai/integrations/muse/github-repository-issue-counts)

# How to Use GitHub repository issue counts in Muse

Fetch issue totals by state and label, excluding pull requests. Use it to measure a backlog without downloading individual reports; GitHub's search system supplies the counts.

|  |  |
| --- | --- |
| Model | GitHub repository issue counts |
| 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 issue counts in Muse

- Use GitHub repository issue counts for vitejs/vite to report open and closed issue totals, excluding pull requests.
- Use GitHub repository issue counts to look this up and give me the result as a table.
- Pull the latest numbers from GitHub repository issue counts and tell me what changed since last week.
- Check GitHub repository issue counts and summarize what you find in three bullet points.
- Pull the newest data from GitHub repository issue counts and give me the result as a table.

## How to set up GitHub repository issue counts in Muse

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

### Use the Muse connector

1. **Create an API key**: Create one under API keys in the Spiral console.

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

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

3. **Give Muse the key**: Paste the key when Muse asks for it, never in the chat itself.

### Use the Spiral skill

1. **Send Muse 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 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 issue counts**: 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/issue_counts",
    "input": {
      "repo": "<repo>"
    }
  }'
```

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

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

## GitHub repository issue counts tools and prices

- [GitHub · Issue counts](https://spiral.ai/tools/alexandria/github-com/repositories/issue_counts) (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}(?:[/?#].*)?$. |
| 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)?/?$. |
| state | open, closed, all | open | Issue state to match. |
| labels |  | — | Labels to count separately, one search each. |

## What can you do with GitHub repository issue counts in Muse?

Get a project or package assessment grounded in GitHub's public records. A chat app can explain release changes, reported problems, repository activity, and advisory findings with links to the evidence.

### 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 Muse guides](https://spiral.ai/integrations/muse)

## GitHub repository issue counts in other agents

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

## More Muse guides

- [GitHub repository file](https://spiral.ai/integrations/muse/github-repository-file)
- [GitHub repository issues](https://spiral.ai/integrations/muse/github-repository-issues)
- [GitHub repository details](https://spiral.ai/integrations/muse/github-repository-details)
- [GitHub repository labels](https://spiral.ai/integrations/muse/github-repository-labels)
- [GitHub repository contributors](https://spiral.ai/integrations/muse/github-repository-contributors)
- [GitHub repository search](https://spiral.ai/integrations/muse/github-repository-search)

## Questions about GitHub repository issue counts in Muse

**Can Muse use GitHub repository issue counts?**

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

**How much does GitHub repository issue counts cost in Muse?**

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

**Do I need an Alexandria account to use GitHub repository issue counts in Muse?**

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

**How long does it take to set up GitHub repository issue counts in Muse?**

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

**Does Muse wait while GitHub repository issue counts runs?**

GitHub repository issue counts runs in the background. Muse 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.

