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/synaptiai/synapti-marketplaceWrote 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/synaptiai/synapti-marketplace/ledger-update)<a href="https://agentmods.dev/commands/synaptiai/synapti-marketplace/ledger-update"><img src="https://agentmods.dev/badge/commands/synaptiai/synapti-marketplace/ledger-update/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/synaptiai/synapti-marketplace/ledger-update"><img src="https://agentmods.dev/badge/commands/synaptiai/synapti-marketplace/ledger-update.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.01570 |
| Opus 5 | $0.00009 | $0.00785 |
| Sonnet 5 | $0.00003 | $0.00314 |
| Haiku 4.5 | $0.00002 | $0.00157 |
Grade A, and why
ledger-update 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 9d 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.
How it starts
The opening of the file, as written. The whole thing — 279 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Update Ledger
Apply new evidence, decisions, or learnings to the ledger with impact analysis.
Impact-Aware Updates: Changes are tracked and produce a diff showing what downstream artifacts are affected and may need regeneration.
Arguments
$ARGUMENTS: What to update - evidence, decision, or general.
Optional flags:
--evidence <pillar>- Add evidence to specific pillar--decision <id>- Update specific decision--risk <id>- Update specific risk--regenerate- Auto-regenerate affected artifacts
Prerequisites
- Ledger initialized (any phase complete)
- Existing artifacts to update
Workflow
-
Identify Change Type
- New evidence
- Updated evidence
- Decision status change
- Risk update
- Synthesis revision
-
Apply Change
- Add/modify artifact
- Record change metadata
-
Trace Impact
- Find all references to changed artifact
- Identify affected downstream documents
-
Generate Impact Report
- What changed
- What's affected
- Recommended actions
-
Optionally Regenerate
- If
--regenerate, update affected artifacts - Maintain traceability
- If
Example Usage
Add new evidence
/ledger-update --evidence market
Update decision status
/ledger-update --decision DEC-scope-power-users-first
Update risk mitigation
/ledger-update --risk RISK-retention-expert-churn
Auto-regenerate affected docs
/ledger-update --regenerate
General update prompt
/ledger-update "We learned SMB WTP is actually $35 not $29"
Output
## Ledger Update Complete
### What Changed
| Artifact | Change Type | Details |
|----------|-------------|---------|
| EV-market-pricing-smb-wtp | updated | confidence: 0.75 → 0.85, claim revised |
| DEC-pricing-freemium | status change | provisional → accepted |
### Impact Analysis
#### Direct Impact (explicit references)
| Affected Artifact | References Changed | Impact |
|-------------------|-------------------|--------|
| SYN-market.md | EV-market-pricing-smb-wtp | Insight confidence may change |
| CROSS-SYNTHESIS.md | SYN-market.md | Cross-pillar connection affected |
| PRD Section 8 | DEC-pricing-freemium | Status now accepted |
#### Indirect Impact (downstream)
| Affected Artifact | Via | Impact |
|-------------------|-----|--------|
| DECISIONS.yaml | SYN-market.md | May affect decisions citing this evidence |
| PLAN.md | PRD Section 8 | Milestone may need update |
### Impact Report Generated
`IMPACT_REPORT.md`
### Recommended Actions
- [ ] Review SYN-market.md insight on pricing
- [ ] Verify CROSS-SYNTHESIS.md pricing connection
- [ ] PRD Section 8 status confirmed (no change needed)
### Next Steps
Run `/ledger-update --regenerate` to auto-update affected artifacts.
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.
- 9d ago First seen · 279 lines · 17 tokens per session scan A 06abb8614a14
ledger-update is a command published in the GitHub repository synaptiai/synapti-marketplace (6 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 17 tokens to every session and 1,570 once invoked, about $0.0001 per session on Opus 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
create-worktree
Follow these steps to create a git worktree.
paper-trail-review
Review and arbitrate problematic references (cascade-exhausted, unresolved UID, awaiting OCR). Generates an up-to-date report, walks through cases by category, and applies arbitration decisions to the registry.
paper-trail-new-paper
Start writing an academic paper (IMRaD structure) on a topic, with anti-hallucination citation verification at every step. Builds on existing audited SOTAs.
paper-trail-registry-cleanup
Nettoyage historique du registre des fiches bibliographiques (les 900 fiches existantes). Cible les vieilles fiches mal nommées (0000, untitled) ET les duplicates avec suffixes numériques (foo2020bar2, 234) qui sont des artefacts de runs INGEST passés. Délègue les décisions au sub-agent textbook-resolver. Les merge…
paper-trail-linkify
Dernière passe du pipeline cible refondu. Insère les wikilinks finaux dans le SOTA (vers PDF si validé, sinon vers ancre dans une section ## Statut des sources régénérée idempotemment en bas du fichier). Présuppose que les passes identify/purge/acquire ont été lancées.
paper-trail-cascade
Acquire PDFs via the 8-source cascade (11 with opt-in extended sources) for a single ref by slug, or a batch filtered by state. Validates page 1 anti-homonymy on each download.