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/register-repo)<a href="https://agentmods.dev/commands/nunoamorim99/agile-ledger/register-repo"><img src="https://agentmods.dev/badge/commands/nunoamorim99/agile-ledger/register-repo/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/register-repo"><img src="https://agentmods.dev/badge/commands/nunoamorim99/agile-ledger/register-repo.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.00022 | $0.00356 |
| Opus 5.5 | $0.00009 | $0.00142 |
| Sonnet 5.5 | $0.00004 | $0.00071 |
| Haiku 4.5 | $0.00002 | $0.00036 |
Grade A, and why
register-repo 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, register the repository at $ARGUMENTS into the ledger repo.
- Resolve it: a local path, or a remote to clone into
clone_target— propose the clone and wait for confirmation before downloading anything. - Derive the folder slug (lowercase-hyphenated repo name). If that slug is taken, ask rather than overwrite.
- Create
<ledger-root>/<slug>/and scaffold the eight ledger files from theagile-ledgerskill'sreferences/*.template.md— only if absent; if the folder already exists, report and stop. - Add a row to
Registry.md: slug, code path, normalized remote (no scheme, no credentials, no trailing.git), statusactive, no sync SHA yet. Never overwrite an existing row. - With
--from-git, mine the repo's history and propose reconstructed epics/stories as drafts in that folder'sIdeas.md, each flagged🔍 reconstructed from git, followingreferences/reconstruction-guide.md— no invented value or acceptance criteria, Inbox-only, the human triages. - Commit in the ledger repo per
ledger_commit(ledger(<slug>): register repo). Push only on confirmation.
Write nothing into the code repo — not a ledger file, not a config file, not a marker. The resolver finds the ledger by walking up from the code repo to the sibling ledger root.
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 · 15 lines · 22 tokens per session scan A 55b1fa30548b
register-repo is a command published in the GitHub repository nunoamorim99/agile-ledger (1 stars, last pushed 4d ago), licensed MIT. It adds 22 tokens to every session and 356 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.