How to Use GitHub repository issues in Grok Build
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.
Prompts to try with GitHub repository issues in Grok Build
Copy an example into Grok Build, or ask in your own words.
Use GitHub repository issues for vitejs/vite to read recently updated open reports and identify any that match the build failures documented in this project.
Use GitHub repository issues to look this up and give me the result as a table. Save the result in ./assets.
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.
How to set up GitHub repository issues in Grok Build
Pick the way that suits you. Each takes about two minutes.
Use Spiral's MCP server
- Add the server
Add --scope project to add Spiral to the current repository only. No header and no client ID or secret: Grok registers itself with Spiral.
grok mcp add --transport http spiral https://api.spiral.ai/mcp
- Sign in
Start grok and run /mcps. Select Spiral and press i. Your browser opens: sign in to Spiral, pick the organization and click Authorize. No API key.
- Check it
grok mcp doctor spiral
Use the Spiral skill
- Send Grok Build 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 issues
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/issues", "input": { "repo": "<repo>" } }'
Then paste one of the prompts above: Grok Build finds GitHub repository issues on Spiral, shows the price and runs it.
GitHub repository issues providers and prices
Spiral runs GitHub repository issues through Alexandria. Open a card for today's price, with every fee included.
Settings you can ask for
Ask Grok Build 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. |
| Sort | created, updated, or comments | created | sort |
| State | open, closed, or all | open | Issue state to match. |
| Per page | 1 to 100 | 30 | Records per page. |
| Direction | asc or desc | desc | direction |
| Include pull requests | on or off | Keep pull requests, which GitHub lists on the same endpoint. |
Every API field of GitHub · Issues is on its tool page: open its card above.
What can you do with GitHub repository issues in Grok Build?
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.
More on GitHub repository issues and Grok Build
Overview
GitHub repository issues in other agents
Questions about GitHub repository issues in Grok Build
Can Grok Build use GitHub repository issues?
Yes. Add Spiral to Grok Build as an MCP server, and Grok Build can find and run GitHub repository issues like any built-in tool.
How much does GitHub repository issues cost in Grok Build?
$0.00873 per call. You pay from your Spiral balance as you go, with no subscription, and a failed run is not charged. Your Grok Build plan is separate.
Do I need an Alexandria account to use GitHub repository issues in Grok Build?
No. Spiral runs GitHub repository issues 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 issues in Grok Build?
About two minutes: add the server, then sign in, then check it.
Does Grok Build wait while GitHub repository issues runs?
GitHub repository issues runs in the background. Grok Build 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 issues in Grok Build
One Spiral account for every tool your agent needs. No subscription; you pay per run.
Paste this into Grok Build:
set up https://spiral.ai/SKILL.md


