Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add InstalabsAI/instagit --skill analyze-git-repogit clone --depth 1 https://github.com/InstalabsAI/instagitWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/instalabsai/instagit/analyze-git-repo)<a href="https://agentmods.dev/skills/instalabsai/instagit/analyze-git-repo"><img src="https://agentmods.dev/badge/skills/instalabsai/instagit/analyze-git-repo/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/instalabsai/instagit/analyze-git-repo"><img src="https://agentmods.dev/badge/skills/instalabsai/instagit/analyze-git-repo.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00135 | $0.00857 |
| Opus 5 | $0.00068 | $0.00428 |
| Sonnet 5 | $0.00027 | $0.00171 |
| Haiku 4.5 | $0.00014 | $0.00086 |
Grade A, and why
analyze-git-repo scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 10d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Analyze Git Repo
Analyze any Git repository in depth — understand architecture, surface real APIs, debug across repo boundaries, and get source citations with exact file paths and line numbers. Powered by Instagit.
Quick Start
Add to MCP client configuration:
{
"mcpServers": {
"instagit": {
"command": "npx",
"args": ["-y", "instagit@latest"]
}
}
}
No API key required — auto-registers anonymous token on first use. Requires Node.js 18+.
For higher rate limits, sign up at instagit.com and add an API key:
{
"mcpServers": {
"instagit": {
"command": "npx",
"args": ["-y", "instagit@latest"],
"env": {
"INSTAGIT_API_KEY": "ig_your_api_key_here"
}
}
}
}
Works with Claude Code, Claude Desktop, Cursor, VS Code, and any MCP-compatible client.
Tool: ask_repo
Analyze any Git repository with AI.
| Parameter | Type | Required | Description |
|---|---|---|---|
repo |
string | yes | Repository URL, shorthand (owner/repo), or any public Git URL |
prompt |
string | yes | What to analyze or ask about the codebase |
ref |
string | no | Branch, commit SHA, or tag (default: repo's default branch) |
Prompting Examples
For detailed examples across architecture, integration, debugging, migration, security, and code quality — see references/examples.md.
Key patterns:
repo: "nginx/nginx"
prompt: "How does nginx handle thousands of concurrent connections with its event-driven architecture? Walk through the event loop, worker process model, and connection state transitions."
repo: "hashicorp/terraform"
prompt: "How do I implement a custom Terraform provider from scratch? What interfaces does the SDK expose, how are CRUD operations mapped to the resource lifecycle, and how does schema definition work?"
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 10d ago First seen · 91 lines · 135 tokens per session scan A 9a900dd77626
analyze-git-repo is a skill published in the GitHub repository InstalabsAI/instagit (19 stars, last pushed 6mo ago), licensed MIT. It adds 135 tokens to every session and 857 once invoked, about $0.0007 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
create-pr
This skill should be used when user asks to "create a PR", "make a pull request", "open PR for this branch", "submit changes as PR", "push and create PR", or explicitly invokes "create-pr".
commit-staged
This skill should be used when user asks to "commit these changes", "write commit message", "stage and commit", "create a commit", "commit staged files", or explicitly invokes "commit-staged".
resolve-pr-comments
This skill should be used when user asks to "address PR comments", "resolve PR feedback", "handle review comments", "fix PR issues", "respond to PR review", or explicitly invokes "resolve-pr-comments".
review-pr
This skill should be used when user asks to "review a PR", "review pull request", "review this pr", "code review this PR", "check PR.
update-pr-summary
This skill should be used when user asks to "update PR summary", "update PR description", "rewrite PR body", "refresh PR title and body", or explicitly invokes "update-pr-summary".
clean-gone-branches
This skill should be used when user asks to "clean gone branches", "remove deleted local branches", "prune branches removed from remote", or explicitly invokes "clean-gone-branches".