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/workspace-sync)<a href="https://agentmods.dev/commands/nunoamorim99/agile-ledger/workspace-sync"><img src="https://agentmods.dev/badge/commands/nunoamorim99/agile-ledger/workspace-sync/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/workspace-sync"><img src="https://agentmods.dev/badge/commands/nunoamorim99/agile-ledger/workspace-sync.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.00284 |
| Opus 5.5 | $0.00009 | $0.00114 |
| Sonnet 5.5 | $0.00004 | $0.00057 |
| Haiku 4.5 | $0.00002 | $0.00028 |
Grade A, and why
workspace-sync 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 Workspace skill, sync all repos in the ledger repo's Registry.md. (1) Run /discover-repos to catch new repositories. (2) For each known repo run the per-repo /sync-main reconciliation — reading git in the code repo at its registered path, writing only into its ledger folder (merges to main since that repo's last-sync SHA, mapped to US/BUG ids case-insensitively); report a repo whose code path is missing as path not found rather than skipping it silently. (3) Flag undocumented work — merges with no id — and propose a reconstructed Draft in that folder's Ideas.md for each (flagged, linked to the commit/PR). (4) Produce ONE consolidated report per repo: new / merged-and-reconciled / undocumented-drafted / unchanged, plus blocked and unreleased counts. Read-only by default — clone, draft, and reconcile only on the user's confirmation. Update each repo's last-sync SHA and the Registry's last swept date after review, then offer ONE commit in the ledger repo (ledger: workspace sync <date>) per ledger_commit.
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 · +1 tokens per session caa5935f8fb9
- 1mo ago First seen · 5 lines · 21 tokens per session scan A bb4ae6dc7a30
workspace-sync is a command published in the GitHub repository nunoamorim99/agile-ledger (1 stars, last pushed 2d ago), licensed MIT. It adds 22 tokens to every session and 284 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.