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/migrate-ledger)<a href="https://agentmods.dev/commands/nunoamorim99/agile-ledger/migrate-ledger"><img src="https://agentmods.dev/badge/commands/nunoamorim99/agile-ledger/migrate-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/migrate-ledger"><img src="https://agentmods.dev/badge/commands/nunoamorim99/agile-ledger/migrate-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.00030 | $0.00441 |
| Opus 5.5 | $0.00012 | $0.00176 |
| Sonnet 5.5 | $0.00006 | $0.00088 |
| Haiku 4.5 | $0.00003 | $0.00044 |
Grade A, and why
migrate-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, migrate a pre-2.0 in-repo ledger into the ledger repository. Target the repo at $ARGUMENTS, or the cwd's repo when no argument is given. Safe to re-run.
- Locate the code repo's
Agile-Ledger/folder. If there is none, say so and stop. - Register the repo first if it isn't in
Registry.mdyet (/register-repobehaviour, no--from-git). - Copy the files verbatim into
<ledger-root>/<slug>/. Never rewrite, re-date, re-number, or "tidy" content during a migration — the team's history moves across exactly as they wrote it. Carry over any extra files the team added alongside the eight. - If the target folder already holds files, stop and report the conflict per file. Never merge two ledgers silently; offer to keep the central copy, take the in-repo copy, or let the user resolve it by hand.
- Commit the ledger repo (
ledger(<slug>): migrate ledger from the code repo) perledger_commit, then verify the files are present and committed. - Only then offer to clean the code repo: create
setup_branch,git rm -r Agile-Ledger, commit locally, and hand the branch over for the user to push and PR. Never push, PR, or merge. Ifgit_executionisoff, name the folder to delete and change nothing in the code repo. - Report what moved, what is still pending, and the new one-line location (
Ledger: <ledger-root> → <slug>).
Until the code repo's copy is removed, treat the central folder as the source of truth and say that the in-repo copy is stale, so no one edits two ledgers at once.
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 · 16 lines · 30 tokens per session scan A b4ccba577ae6
migrate-ledger is a command published in the GitHub repository nunoamorim99/agile-ledger (1 stars, last pushed 4d ago), licensed MIT. It adds 30 tokens to every session and 441 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.