[Integrations](https://spiral.ai/integrations) › [opencode](https://spiral.ai/integrations/opencode) › [GitHub repository labels](https://spiral.ai/integrations/opencode/github-repository-labels)

# How to Use GitHub repository labels in opencode

Fetch a repository's label names, descriptions, colors, and default-label flags. Use the actual label vocabulary to find relevant issues and build meaningful backlog counts.

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

## Prompts to try with GitHub repository labels in opencode

- Use GitHub repository labels to look this up and give me the result as a table. Save the result in ./assets.
- Pull the latest numbers from GitHub repository labels and tell me what changed since last week.
- Check GitHub repository labels and summarize what you find in three bullet points.
- Pull the newest data from GitHub repository labels and give me the result as a table.
- Check GitHub repository labels every morning and tell me only when something changed.

## How to set up GitHub repository labels in opencode

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

### Use Spiral's MCP server

1. **Add the server**: Leave out `--global` to add Spiral to the current project only. No header and no client ID or secret: opencode registers itself with Spiral.

```bash
opencode mcp add spiral --global --url https://api.spiral.ai/mcp
```

2. **Sign in**: Your browser opens. Sign in to Spiral, pick the organization and click Authorize, then return to the terminal. No API key. Inside opencode, `/mcps` starts the same sign-in.

```bash
opencode mcp auth spiral
```

3. **Check it**: Spiral shows as connected.

```bash
opencode mcp list
```

### Use the Spiral skill

1. **Send opencode 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 labels**: 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/labels",
    "input": {
      "repo": "<repo>"
    }
  }'
```

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

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

## GitHub repository labels tools and prices

- [GitHub · Labels](https://spiral.ai/tools/alexandria/github-com/repositories/labels) (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)?/?$. |
| per_page | 1 to 100 | 100 | Records per page. |

## What can you do with GitHub repository labels in opencode?

Build a dependency review beside the code using GitHub files, release notes, issue evidence, and package advisories. A coding agent can compare those records with the project's manifests and turn the findings into proposed changes.

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

## GitHub repository labels in other agents

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

## More opencode guides

- [GitHub repository issues](https://spiral.ai/integrations/opencode/github-repository-issues)
- [GitHub repository search](https://spiral.ai/integrations/opencode/github-repository-search)
- [GitHub repository issue counts](https://spiral.ai/integrations/opencode/github-repository-issue-counts)
- [GitHub repository security advisories](https://spiral.ai/integrations/opencode/github-repository-security-advisories)
- [GitHub repository file](https://spiral.ai/integrations/opencode/github-repository-file)
- [GitHub security advisory](https://spiral.ai/integrations/opencode/github-security-advisory)

## Questions about GitHub repository labels in opencode

**Can opencode use GitHub repository labels?**

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

**How much does GitHub repository labels cost in opencode?**

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

**Do I need an Alexandria account to use GitHub repository labels in opencode?**

No. Spiral runs GitHub repository labels on its own Alexandria account. You sign in to Spiral once and never paste a key.

**How long does it take to set up GitHub repository labels in opencode?**

About two minutes: add the server, then sign in, then check it.

**Does opencode wait while GitHub repository labels runs?**

GitHub repository labels runs in the background. opencode 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.

