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/ledger-check)<a href="https://agentmods.dev/commands/nunoamorim99/agile-ledger/ledger-check"><img src="https://agentmods.dev/badge/commands/nunoamorim99/agile-ledger/ledger-check/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/ledger-check"><img src="https://agentmods.dev/badge/commands/nunoamorim99/agile-ledger/ledger-check.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.00014 | $0.00295 |
| Opus 5 | $0.00007 | $0.00148 |
| Sonnet 5 | $0.00003 | $0.00059 |
| Haiku 4.5 | $0.00001 | $0.00030 |
Grade A, and why
ledger-check 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.
What it actually says
Using the Agile-Ledger skill, audit all Agile-Ledger/*.md files for drift: duplicate or mis-sequenced typed IDs, dangling Parent/dependency links, plus any ID link that doesn't resolve to an existing #id anchor, childless epics, a story on the board but missing under its epic (or vice versa), a board column not matching the story's recorded state, orphan Increment lines, and stale Next free ID counters. Report findings clearly; fix only on explicit request.
Also reconcile the two-file split: epic index line state vs. the story's group in User-Stories.md, a Ready+ story missing its index line (or vice versa), and a Draft story that wrongly has a detail entry.
Then verify the overview index table at the top of Epic-Backlog.md, User-Stories.md, and Bugs.md against the entries below it: every entry has exactly one row, no row points at a missing entry, each row's state / priority / estimate / assignee / title matches its entry, every ID link resolves to a real #id anchor, rows are in section order (active first, done last, highest priority first within a group), and the roll-up counts and points equal the rows they summarize.
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 · 9 lines · 14 tokens per session scan A 8decdbf46c00
ledger-check is a command published in the GitHub repository nunoamorim99/agile-ledger (1 stars, last pushed 1mo ago), licensed MIT. It adds 14 tokens to every session and 295 once invoked, about $0.0001 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 commands, from other repositories
diagnose-underperformer
Diagnose why a specific Google Ads or Meta Ads campaign / ad set / ad is underperforming and prescribe the next concrete action. Use when the user says something like "why is X not converting?", "this campaign is wasting money", or "why are impressions so low?". Read-only — no changes are made.
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.
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.
duck-off
Turn off Rubber Duck mode and answer normally.
finish-tasks
Finalize a work item after all tasks are done — cleanup (currently closing the ticket) and mark the work complete.