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/sync-main)<a href="https://agentmods.dev/commands/nunoamorim99/agile-ledger/sync-main"><img src="https://agentmods.dev/badge/commands/nunoamorim99/agile-ledger/sync-main/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/sync-main"><img src="https://agentmods.dev/badge/commands/nunoamorim99/agile-ledger/sync-main.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.00316 |
| Opus 5.5 | $0.00008 | $0.00126 |
| Sonnet 5.5 | $0.00004 | $0.00063 |
| Haiku 4.5 | $0.00002 | $0.00032 |
Grade A, and why
sync-main 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 12d 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, reconcile main against the ledger. Read git in the code repo; write only in the resolved ledger folder — take the code path from Registry.md or the cwd. Fetch main, list merges since the Last main sync cursor in Sprint.md, and map each commit to its US via the bracketed or parenthesized ID (case-insensitive). Flag two cases: (1) merged but the ledger does not show it Done → propose marking Done and filling the Increment; (2) merged with no US ID → surface it as off-plan work to back-fill or query. Read-only by default; update the sync cursor and sync log only after the user reviews.
Run the git commands from the code repo's directory where possible — the allowed-tools whitelist covers the plain git fetch / log / diff / status / branch / show forms, so a git -C <path> ... variant (needed when the code repo is elsewhere) falls outside it and will ask for approval once. Never reach for a git subcommand that writes.
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.
- 12d ago Changed · +2 lines 771584d2ae33
- 1mo ago First seen · 6 lines · 19 tokens per session scan A 6ad453d1e932
sync-main is a command published in the GitHub repository nunoamorim99/agile-ledger (1 stars, last pushed 2d ago), licensed MIT. It adds 19 tokens to every session and 316 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
run-tasks
Execute GitHub issues using full EPCT workflow (Explore-Plan-Code-Test). Converts issue requirements into completed PR.
contribute-to
Join an EXISTING, in-progress work item (issue or PR) as a contributor — walk the contribution loop toward a human-stated goal and success criteria, without the full spec chain.
ship
Open a pull request for the current branch, drive it green, and merge it.
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.
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.
sync-github
Ejecuta SonIA Sync: refleja el tablero local en GitHub Issues usando gh CLI.