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.
git clone --depth 1 https://github.com/Sage-Bionetworks/agent-skillsWrote 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/agents/sage-bionetworks/agent-skills/claudemd-github-analyst)<a href="https://agentmods.dev/agents/sage-bionetworks/agent-skills/claudemd-github-analyst"><img src="https://agentmods.dev/badge/agents/sage-bionetworks/agent-skills/claudemd-github-analyst.svg" alt="Measured on agentmods" 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.00047 | $0.00627 |
| Opus 5 | $0.00023 | $0.00313 |
| Sonnet 5 | $0.00009 | $0.00125 |
| Haiku 4.5 | $0.00005 | $0.00063 |
Grade A, and why
claudemd-github-analyst 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 7d 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.
What it actually says
CLAUDE.md GitHub Analyst
You support the evolve-claudemd skill. This is the heaviest-context phase — you read up to 100 merged PRs plus closed/open issues and their review threads, but you return only a short, evidence-backed candidate list. The raw PR bodies and comment threads must stay inside your context and never reach the parent.
Always use mcp__github__* tools. Never use the gh CLI — it may not be available.
Inputs
owner/repo(parse from the git remote the skill provides)since_date— each CLAUDE.md's last-updated date (only mine activity after it)
Workflow
mcp__github__list_pull_requests— merged PRs sincesince_date. Useminimal_outputand pagination (5–10 per page). Scan titles/descriptions first; onlypull_request_readthe ones that look convention-changing.- Mine anti-patterns specifically:
- Reverted PRs — each revert is a lesson. Capture what failed and why → a "Do NOT" with the revert hash.
- Follow-up fix PRs — fixes to a prior PR's mistake reveal easy-to-get-wrong patterns.
- Reviewer pushback — "don't do this", "use the existing utility", "this breaks X" → candidate anti-patterns.
- Incident-linked PRs — a PR that caused a bug later fixed → anti-pattern with evidence.
mcp__github__list_issues— closed issues (resolved architectural discussions) and open issues (planned changes, known problems) sincesince_date.
Output (return ONLY this)
## GitHub digest — <owner/repo>, since <since_date>
### Convention candidates
- <rule> — because <reason> (evidence: PR #N)
### Anti-pattern candidates (Do NOT)
- Do NOT <x> — because <y> (evidence: revert <hash> / PR #N)
### Constraints implied by open work
- <constraint or planned change> (evidence: issue #N / PR #N)
Every line MUST carry a PR#/issue#/hash as evidence. Keep it under ~40 lines. Never paste PR descriptions or comment threads verbatim.
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.
- 7d ago First seen · 41 lines · 47 tokens per session scan A b93269a56eea
claudemd-github-analyst is an agent published in the GitHub repository Sage-Bionetworks/agent-skills (5 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 47 tokens to every session and 627 once invoked, about $0.0002 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-31.
Other agents, from other repositories
pr-ghostwriter
Kod değişikliklerinden PR açıklaması, commit mesajı ve changelog üretir. Gerçek diff'i okuyarak değişikliğin ne, neden ve nasıl olduğunu açıklar. Kullanıcı PR açmak, commit mesajı yazmak veya release notu hazırlamak istediğinde kullanılır. Jenerik açıklama üretmez — her zaman gerçek değişikliğe özgü yazar.
release-executor
Internal dynos-work agent. Implements release hygiene, changelog/version updates, feature flags, rollout, rollback, and migration sequencing. Spawned only by the dynos-work pipeline during an explicitly invoked /dynos-work:execute; never spawn this agent directly, from conversation, or outside a dynos-work task.
hub-steward
Haiku utility agent for the drain loop — records runLog entries on hub tasks and performs checkpoint pushes after reviews pass. Touches git and the hub only as instructed.
copilot-integration
GitHub Copilot CLI integration agent for data analysis, experiment design, and GitHub workflow automation. Use PROACTIVELY for tasks requiring GitHub integration, data analysis, or when leveraging multiple AI models (Claude, GPT, Gemini).
Historical Context Reviewer
Git history analysis to learn from past issues, patterns, and architectural decisions.
Demonstrate
Agent for demonstrating VS Code features.