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 simiancraft/simiancraft-skills --skill burn-down-github-issuesgit clone --depth 1 https://github.com/simiancraft/simiancraft-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/skills/simiancraft/simiancraft-skills/burn-down-github-issues)<a href="https://agentmods.dev/skills/simiancraft/simiancraft-skills/burn-down-github-issues"><img src="https://agentmods.dev/badge/skills/simiancraft/simiancraft-skills/burn-down-github-issues/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/simiancraft/simiancraft-skills/burn-down-github-issues"><img src="https://agentmods.dev/badge/skills/simiancraft/simiancraft-skills/burn-down-github-issues.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.00232 | $0.03671 |
| Opus 5.5 | $0.00093 | $0.01468 |
| Sonnet 5.5 | $0.00046 | $0.00734 |
| Haiku 4.5 | $0.00023 | $0.00367 |
Grade A, and why
burn-down-github-issues 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 4d 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 — 208 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Burn Down GitHub Issues
A burndown is a board. Every issue the loop touches is a card, every card is in exactly one lane
(a column of the board; the fix pipeline also calls an issue's worktree its lane), and the lanes are the leaf states of a statechart (lib/machine.ts, in XState's vocabulary) that
says which seat runs on a card in that lane, what it may decide, and where each decision moves the
card. The board is a GitHub Projects board per operator per repository, so a person who starts a
burndown comes back to their own board and the loop resumes from it; the console prints the same
cards in the same words. The tracker holds the facts (labels, pull requests, claims, records); the
board is a projection of those facts that a person can read at a glance, and every run starts by
placing every card where its facts say before any seat moves one.
Seats are polymorphic. A seat is an engine running whatever prompt the card's lane calls for
(appraiser, close confirmer, carver, cut confirmer, worker, worker in revision, reviewer), then
letting go; the card's position is the only input that changes what a seat does. Three rules hold
across every seat: the reviewer and the confirmers run on a different engine than the author
seats, claims on the issue thread are the lock that keeps two seats off one card, and merging is
the one serial lane. references/state-machine.md is the machine in prose.
The loop is shared; the repository is config. Nothing in this skill is copied into a repository.
Everything true of a repository (remotes, branches, commands, path aliases, invalidation paths)
lives in burn-down-github-issues.config.ts at that repository's root, and the loop refuses to
start without one, naming the missing file and the fields it lacks.
Standards the loop enforces
These travel with the skill because an adopter cannot be assumed to have house rules of its own. The first three are enforced by the driver, so no prompt drift can lose them; the rest are written into the prompts and checked by the reviewer.
What ships with it
30 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.
- board.ts 6.5 KB runs code
- callbacks/on-size-over-ceiling 843 B
- callbacks/README.md 1.1 KB
- card.ts 4.3 KB runs code
- chart-machine.ts 3.9 KB runs code
- claim-race.ts 6.1 KB runs code
- export-machine.ts 1.8 KB runs code
- lanes.ts 5.2 KB runs code
- lib/board-writer.ts 11 KB runs code
- lib/carving.ts 24 KB runs code
- lib/lanes.ts 4.3 KB runs code
- lib/machine.test.ts 10 KB runs code
- lib/machine.ts 48 KB runs code
- lib/place-callbacks.test.ts 2.5 KB runs code
- lib/place-callbacks.ts 3.0 KB runs code
- lib/pressure.test.ts 40 KB runs code
- lib/refs.test.ts 1010 B runs code
- lib/refs.ts 1.9 KB runs code
- lib/scenarios.test.ts 15 KB runs code
- lib/simulate.test.ts 6.9 KB runs code
- lib/simulate.ts 7.0 KB runs code
- lib/world-sweep.test.ts 21 KB runs code
- loop.source.test.ts 762 B runs code
- loop.ts 63 KB runs code
- references/adopting.md 25 KB
- references/architecture.md 19 KB
- references/operating.md 17 KB
- references/state-machine.md 27 KB
- status.ts 4.9 KB runs code
- watch.ts 7.2 KB runs code
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.
- 4d ago First seen · 208 lines · 232 tokens per session scan A 4cecde2c48ab
burn-down-github-issues is a skill published in the GitHub repository simiancraft/simiancraft-skills (8 stars, last pushed 5d ago), licensed MIT. It adds 232 tokens to every session and 3,671 once invoked, about $0.0009 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-20.
Other skills, from other repositories
glab
Expert guidance for using the GitLab CLI (glab) to manage GitLab issues, merge requests, CI/CD pipelines, repositories, and other GitLab operations from the command line. Use this skill when the user needs to interact with GitLab resources or perform GitLab workflows.
run
Drive a GitHub issue — bare or tracked on a Project board — from triage to a merge-ready PR through a gated pipeline (design hardening, tests green, code-review clean), scaling the machinery to the task's tier and asking at most one batched question. Auto-links the issue to close on merge, advances the board card…
github-issue-triage
A GitHub issue organiser for open problems and requests in a software project. GitHub is a service where teams store code and track issues.
predictable-revenue
Build a scalable outbound B2B sales machine with specialized roles (SDR, AE, CSM). Use when the user mentions "outbound sales", "Cold Calling 2.0", "cold email sequences", "sales pipeline", "SDR process", "sales development", "build an outbound sales team", or "fill my pipeline". Also trigger when setting up a B2B…
traction-eos
Implement the Entrepreneurial Operating System (EOS) to align vision and execution across a company. Use when the user mentions "EOS", "Entrepreneurial Operating System", "V/TO", "quarterly rocks", "Level 10 meetings", "accountability chart", "IDS process", "my company feels chaotic", "we keep having the same…
catchup
Summarize and review what changed while you were away. Use after a weekend, vacation, or flight to check missed PRs, git commits, Linear tickets, and meetings — one prioritized brief, not a firehose.