How to Use GitHub repository details in Grok
Fetch repository metadata such as stars, forks, language, license, activity dates, and archive status. Use it for an initial project assessment before reading releases, files, or individual issues.
Prompts to try with GitHub repository details in Grok
Copy an example into Grok, or ask in your own words.
Use GitHub repository details to compare psf/requests and encode/httpx by stars, forks, license, archive status, and last push date.
Use GitHub repository details to look this up and give me the result as a table.
Pull the latest numbers from GitHub repository details and tell me what changed since last week.
Check GitHub repository details and summarize what you find in three bullet points.
Pull the newest data from GitHub repository details and give me the result as a table.
How to set up GitHub repository details in Grok
Pick the way that suits you. Each takes about two minutes.
Use the Grok connector
- Add a custom connector
In Grok open Settings › Connect Apps, then Add a custom connector. Name it Spiral, paste this URL, leave Headers empty and click Add MCP.
https://api.spiral.ai/mcp
- Sign in to Spiral and approve
Grok opens Spiral: sign in, pick the organization and click Authorize. Spiral gives the connection its own API key; Grok never sees it, and you can remove the connection under Settings › Connected apps.
- Check that it is connected
Connect Apps › Custom shows Spiral as Connected. It works in every Grok chat and Grok bot.
Use the Spiral skill
- Send Grok 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 details
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/repo", "input": { "repo": "<repo>" } }'
Then paste one of the prompts above: Grok finds GitHub repository details on Spiral, shows the price and runs it.
GitHub repository details providers and prices
Spiral runs GitHub repository details through Alexandria. Open a card for today's price, with every fee included.
What can you do with GitHub repository details in Grok?
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.
Maintain a package security watch
Check a defined package list for malware reports and known advisory changes, then compare repository status, manifests, and published releases with the previous review. Produce a change report with links to the supporting records.
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 details and Grok
Overview
GitHub repository details in other agents
Questions about GitHub repository details in Grok
Can Grok use GitHub repository details?
Yes. Add Spiral to Grok as an MCP server, and Grok can find and run GitHub repository details like any built-in tool.
How much does GitHub repository details cost in Grok?
$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 plan is separate.
Do I need an Alexandria account to use GitHub repository details in Grok?
No. Spiral runs GitHub repository details 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 details in Grok?
About two minutes: add a custom connector, then sign in to Spiral and approve, then check that it is connected.
Does Grok wait while GitHub repository details runs?
GitHub repository details runs in the background. Grok 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 details in Grok
One Spiral account for every tool your agent needs. No subscription; you pay per run.
Paste this into Grok:
set up https://spiral.ai/SKILL.md


