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/init-ledger)<a href="https://agentmods.dev/commands/nunoamorim99/agile-ledger/init-ledger"><img src="https://agentmods.dev/badge/commands/nunoamorim99/agile-ledger/init-ledger/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/init-ledger"><img src="https://agentmods.dev/badge/commands/nunoamorim99/agile-ledger/init-ledger.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.00017 | $0.00289 |
| Opus 5.5 | $0.00007 | $0.00116 |
| Sonnet 5.5 | $0.00003 | $0.00058 |
| Haiku 4.5 | $0.00002 | $0.00029 |
Grade A, and why
init-ledger 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 3d 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 Workspace skill, create the ledger repository: the separate repo that holds one folder per code repo, so code repos stay clean.
Place it at $ARGUMENTS if given; otherwise propose ./agile-ledger when the cwd looks like a workspace root (a directory holding your code repos), and ask if it doesn't. Write Registry.md and Config.md from the agile-ledger skill's references/ templates — keep Registry.md's # Agile-Ledger Registry heading exactly as it is, since that heading is the marker the resolver looks for. Ask for the GitHub org/owner and the clone target and write them into Config.md.
Offer git init plus a first commit, and tell the user to create the remote and push it themselves. Do not scan, clone, or register anything — that is /discover-repos and /register-repo.
If a ledger root already exists at or above the cwd, report where it is and stop: one ledger per workspace. If the user has pre-2.0 Agile-Ledger/ folders inside code repos, point them at /migrate-ledger next.
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.
- 3d ago First seen · 12 lines · 17 tokens per session scan A 07c2593599ab
init-ledger is a command published in the GitHub repository nunoamorim99/agile-ledger (1 stars, last pushed 4d ago), licensed MIT. It adds 17 tokens to every session and 289 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-10-12.
Other commands, from other repositories
run-tasks
Execute GitHub issues using full EPCT workflow (Explore-Plan-Code-Test). Converts issue requirements into completed PR.
genshijin-commit
A command that writes a commit message for changes already placed in Git's staging area. It follows the repository's existing language and uses a short imperative subject without AI attribution.
commit
Smart conventional commit with security validation, branch flow enforcement, and auto-detection. Use for git commit, commit changes, save work, stage and commit.
flow
Universal workflow entry point. Use /flow for skill-driven GitHub development. Verbs: start, commit, pr, review, address, merge, resolve, release, status, learn, setup, explain, debug, design, brainstorm, issue.
amend
Amend last commit safely. Use for amend, fix last commit, update commit, modify commit.
chore
Chore commit. Use for maintenance, deps, dependencies, config, cleanup, housekeeping.