How to Use GitHub repository labels in Manus
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.
Prompts to try with GitHub repository labels in Manus
Copy an example into Manus, or ask in your own words.
Use GitHub repository labels for microsoft/vscode to explain how the project categorizes bug reports and feature requests.
Use GitHub repository labels to look this up and give me the result as a table.
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.
How to set up GitHub repository labels in Manus
Pick the way that suits you. Each takes about two minutes.
Use the Manus connector
- Add a custom MCP connector
In Manus open Settings › Connectors (or the connectors icon under the chat box), then Add connectors › Custom MCP and Add MCP by URL. Name it Spiral, set Transport to HTTP and paste this Server URL:
https://api.spiral.ai/mcp
- Sign in to Spiral and approve
Manus asks you to sign in the first time it uses Spiral. Spiral opens: sign in, pick the organization and click Authorize. No API key. Spiral gives the connection its own key; Manus never sees it, and you can remove it under Settings › Connected apps in the console.
Use the Spiral skill
- Send Manus this message
Your agent reads Spiral's skill and sets itself up.
set up https://spiral.ai/SKILL.md
- Sign in or paste a key
Approve Spiral in the browser, or give the agent a key from the console.
Use the Spiral CLI
- Install and sign in
Installs the Spiral CLI, signs you in and adds its skill to your coding agents.
npx -y spiral-cli@latest init
Call the Spiral API
- Create an API key
In the console, under API keys.
- Run GitHub repository labels
One request; the result comes back by polling or a webhook.
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: Manus finds GitHub repository labels on Spiral, shows the price and runs it.
GitHub repository labels providers and prices
Spiral runs GitHub repository labels through Alexandria. Open a card for today's price, with every fee included.
Settings you can ask for
Ask Manus for any of these in your prompt.
| Setting | Allowed values | Default | Description |
|---|---|---|---|
| Page | 1 to 1000 | 1 | 1-based page; has_next in the response says whether page+1 exists. |
| Per page | 1 to 100 | 100 | Records per page. |
Every API field of GitHub · Labels is on its tool page: open its card above.
What can you do with GitHub repository labels in Manus?
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.
More on GitHub repository labels and Manus
Overview
GitHub repository labels in other agents
Questions about GitHub repository labels in Manus
Can Manus use GitHub repository labels?
Yes. Add Spiral to Manus as an MCP server, and Manus can find and run GitHub repository labels like any built-in tool.
How much does GitHub repository labels cost in Manus?
$0.00873 per call. You pay from your Spiral balance as you go, with no subscription, and a failed run is not charged. Your Manus plan is separate.
Do I need an Alexandria account to use GitHub repository labels in Manus?
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 Manus?
About two minutes: add a custom MCP connector, then sign in to Spiral and approve.
Does Manus wait while GitHub repository labels runs?
GitHub repository labels runs in the background. Manus 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.
Start using GitHub repository labels in Manus
One Spiral account for every tool your agent needs. No subscription; you pay per run.
Paste this into Manus:
set up https://spiral.ai/SKILL.md


