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/nunoamorim99/agile-ledgerWrote 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/commands/nunoamorim99/agile-ledger/bug)<a href="https://agentmods.dev/commands/nunoamorim99/agile-ledger/bug"><img src="https://agentmods.dev/badge/commands/nunoamorim99/agile-ledger/bug/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/commands/nunoamorim99/agile-ledger/bug"><img src="https://agentmods.dev/badge/commands/nunoamorim99/agile-ledger/bug.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.00019 | $0.00226 |
| Opus 5.5 | $0.00008 | $0.00090 |
| Sonnet 5.5 | $0.00004 | $0.00045 |
| Haiku 4.5 | $0.00002 | $0.00023 |
Grade A, and why
bug 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 8d 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
Capture a bug using the Agile-Ledger skill.
Append $ARGUMENTS verbatim — in whatever language it was written, as the reporter's own words — together with today's absolute date (YYYY-MM-DD) to the top of the 🐛 Inbox section of the resolved repo folder's Bugs.md.
Resolve the ledger first (the sibling ledger repo, then this repo's folder in it — --repo <slug> overrides); the file lives in <ledger-root>/<repo-slug>/, never in the code repo.
Rules: no ID, no deduplication, no rewriting, no investigation, no questions. Instant and safe mid-work. Re-read the file before writing. If the repo's folder doesn't exist in the ledger yet, scaffold its eight files from the skill's reference templates first (including Bugs.md); if there is no ledger repo at all, say so and offer /init-ledger.
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.
- 8d ago Changed · +2 lines 52750f7bacda
- 1mo ago First seen · 10 lines · 19 tokens per session scan A 78740a20870a
bug is a command published in the GitHub repository nunoamorim99/agile-ledger (1 stars, last pushed 5d ago), licensed MIT. It adds 19 tokens to every session and 226 once invoked, about $0.0001 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-08-31.
Other commands, from other repositories
duck-off
Turn off Rubber Duck mode and answer normally.
help
Rubber Duck: what it does, how to steer it, how to stop it.
sdlc-incident
Incident response and management - triage, mitigation, communication, action items.
launch-meta-campaign
Launch a complete Meta Ads campaign — campaign, ad set, and ad(s) — built paused and ready to review. Use when the user wants a new Facebook/Instagram campaign.
launch-pmax
Launch a Google Ads Performance Max campaign with a complete asset group, audience signals, and (for ecom) listing groups. Built paused for review. Use when the user wants a new PMax campaign.
negative-keyword-sweep
Find wasted spend in Google Ads search terms and add negatives at the right scope (account list, campaign, or ad group). Use when the user says "find junk keywords", "stop wasting on bad searches", or wants a search-terms cleanup.