How to Use GitHub repository contributors in Muse Code
Fetch repository contributors ranked by commit count, with account names and contribution totals. Use it to assess how concentrated a project's recorded contributions are; GitHub caches these results for hours.
Prompts to try with GitHub repository contributors in Muse Code
Copy an example into Muse Code, or ask in your own words.
Use GitHub repository contributors to look this up and give me the result as a table. Save the result in ./assets.
Pull the latest numbers from GitHub repository contributors and tell me what changed since last week.
Check GitHub repository contributors and summarize what you find in three bullet points.
Pull the newest data from GitHub repository contributors and give me the result as a table.
Check GitHub repository contributors every morning and tell me only when something changed.
How to set up GitHub repository contributors in Muse Code
Pick the way that suits you. Each takes about two minutes.
Use Spiral's MCP server
- Install Muse Code
curl -fsSL https://dev.meta.ai/install.sh | bash
- Ask Muse to add the server
Start muse and ask:
Add the Spiral MCP server at https://api.spiral.ai/mcp
- Sign in
In your terminal, run:
muse mcp login spiral
Use the Spiral skill
- Send Muse Code 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 contributors
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/contributors", "input": { "repo": "<repo>" } }'
Then paste one of the prompts above: Muse Code finds GitHub repository contributors on Spiral, shows the price and runs it.
GitHub repository contributors providers and prices
Spiral runs GitHub repository contributors through Alexandria. Open a card for today's price, with every fee included.
Settings you can ask for
Ask Muse Code 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 | 30 | Records per page. |
Every API field of GitHub · Contributors is on its tool page: open its card above.
What can you do with GitHub repository contributors in Muse Code?
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.
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 contributors and Muse Code
Overview
GitHub repository contributors in other agents
Questions about GitHub repository contributors in Muse Code
Can Muse Code use GitHub repository contributors?
Yes. Add Spiral to Muse Code as an MCP server, and Muse Code can find and run GitHub repository contributors like any built-in tool.
How much does GitHub repository contributors cost in Muse Code?
$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 Code plan is separate.
Do I need an Alexandria account to use GitHub repository contributors in Muse Code?
No. Spiral runs GitHub repository contributors 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 contributors in Muse Code?
About two minutes: install Muse Code, then ask Muse to add the server, then sign in.
Does Muse Code wait while GitHub repository contributors runs?
GitHub repository contributors runs in the background. Muse Code 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 contributors in Muse Code
One Spiral account for every tool your agent needs. No subscription; you pay per run.
Paste this into Muse Code:
set up https://spiral.ai/SKILL.md


