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 jschulte/claude-plugins --skill issue-burndowngit clone --depth 1 https://github.com/jschulte/claude-pluginsWrote 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/jschulte/claude-plugins/issue-burndown)<a href="https://agentmods.dev/skills/jschulte/claude-plugins/issue-burndown"><img src="https://agentmods.dev/badge/skills/jschulte/claude-plugins/issue-burndown/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/jschulte/claude-plugins/issue-burndown"><img src="https://agentmods.dev/badge/skills/jschulte/claude-plugins/issue-burndown.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.00063 | $0.02508 |
| Opus 5.5 | $0.00025 | $0.01003 |
| Sonnet 5.5 | $0.00013 | $0.00502 |
| Haiku 4.5 | $0.00006 | $0.00251 |
Grade A, and why
issue-burndown 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 24d 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 — 189 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Issue Burndown
End-to-end pipeline: inventory the backlog → map claims → group by shared fix → plan per batch → one fixer subagent per batch → PR per batch → adversarial review → merge to the integration branch. The backlog is a claims problem before it is a fix problem: in a busy repo a large slice of "open" issues are already fixed, claimed by an open PR, duplicates, or waiting on a human decision. Fixing before mapping wastes agent-runs and collides with in-flight work.
Repo conventions override this skill. Phase 0 exists to find them.
When NOT to use
- One or two issues → just fix them (
deliver-metakes a single issue end to end). - The user wants analysis only → stop after Phase 2 and report; the disposition table and batch table ARE the deliverable.
Phase 0 — Read the repo's own rules first
Read before counting anything: the project's agent instructions (CLAUDE.md, AGENTS.md), any issue-state / tracker conventions doc, any production-readiness or audit ledger, and any repo-local sweep or definition-of-done skill — its rules on guards, exit codes, concurrency and worktree hygiene apply here. Also re-read active handoff notes: other sessions may own issue ranges right now.
Phase 1 — Inventory and claim map
gh issue list --state open --limit 300 --json number,title,labels,createdAt,body
gh pr list --state open --limit 100 --json number,title,body,baseRefName,isDraft
gh pr list --state merged --limit 60 --json number,title,body,mergedAt --search "merged:>=<last release date>"
Claims live in narrative prose, not machine links. Measured on a real repo:
GraphQL closingIssuesReferences returned zero rows and a
closes/fixes/resolves #N regex matched zero of 34 open PR bodies — while a
third of them fixed open issues. The claim map is produced by READING every
non-bot open PR body and recent merged PR titles+bodies, and classifying each
#N reference as: fixes / partial / context / follow-up-spawned-by. A regex
pass is a starting index, never the answer. Dependabot bodies are full of
external #N noise — exclude bots up front.
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.
- 24d ago First seen · 189 lines · 63 tokens per session scan A d382034a1623
issue-burndown is a skill published in the GitHub repository jschulte/claude-plugins (0 stars, last pushed 25d ago), licensed MIT. It adds 63 tokens to every session and 2,508 once invoked, about $0.0003 per session on Opus 5.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-10-12.
Other skills, from other repositories
merge-batch
Prepare and merge an owner-selected PR batch with contributor credit and exact-candidate admission. Use for a pasted PR list; combined focused validation is diagnostic, and every actual landing still requires its applicable checks and authorization.
prowler-commit
Creates professional git commits for Prowler following conventional-commits format, with prek pre-commit hooks. Trigger: When creating commits, after completing code changes, when user asks to commit.
gh-auth-isolation
Safely manage multiple GitHub identities (EMU + personal) in agent workflows.
github-skill
Work with GitHub via the gh CLI — clone repositories, create/list/merge pull requests, create/list issues, and run any other gh command (API calls, workflow runs, releases, repo administration). List operations return parsed JSON.
comet-github
A routing guide for Comet-related GitHub work. It directs requests about pull requests, issues, CI failures, ideas, and fixes to the appropriate review or implementation process.
re0-merge
Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…