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.
npx skills add synaptiai/synapti-marketplace --skill evidence-ledgergit 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/skills/synaptiai/synapti-marketplace/evidence-ledger)<a href="https://agentmods.dev/skills/synaptiai/synapti-marketplace/evidence-ledger"><img src="https://agentmods.dev/badge/skills/synaptiai/synapti-marketplace/evidence-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/skills/synaptiai/synapti-marketplace/evidence-ledger"><img src="https://agentmods.dev/badge/skills/synaptiai/synapti-marketplace/evidence-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.00137 | $0.02855 |
| Opus 5 | $0.00068 | $0.01427 |
| Sonnet 5 | $0.00027 | $0.00571 |
| Haiku 4.5 | $0.00014 | $0.00285 |
Grade A, and why
evidence-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 8d 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 — 135 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Evidence Ledger
The register every material claim in the package traces back to. Owns claim states, source authority, and the separation of fact from interpretation.
Iron Law
NO ASSERTION WITHOUT A LEDGER ROW AND A CLAIM STATE. If you cannot cite [EV-####], write "Unknown" instead of writing prose.
The failure this prevents is not fabrication. It is the confident, plausible, unsourced sentence that a reader acts on — and that nobody can check six months later without redoing the whole inspection.
What needs a row
A material claim is one that could change an investment, acquisition, partnership, procurement, or security decision; change how a teammate modifies, deploys, operates, or troubleshoots the system; change what a partner builds against; or change what a customer believes the product does, guarantees, stores, protects, or supports.
Everything else is prose and needs no row. "This document explains the deployment model" is prose. "Deployments are zero-downtime" is a claim, and a strong one.
The six states
| State | Entry condition | May appear |
|---|---|---|
V verified |
Directly supported by authoritative current evidence, or an executed check whose output is retained | Internal and public, unqualified |
C corroborated |
Two independent current sources agree, at least one authoritative for this claim type | Internal and public, unqualified |
R reported |
Stated by a stakeholder or an existing document, not independently verified | Internal, labelled. Never public |
I inferred |
Reasoned from indirect evidence, chain stated | Internal, labelled. Never public |
U unknown |
Unavailable, inaccessible, or unresolvably contradictory | Internal, as a stated unknown |
N/A |
Demonstrably irrelevant, with a reason and evidence | Internal, at section level |
Two documents agreeing is not C when one was copied from the other. Independence means neither derives from the other; circular sourcing between package documents is a specific thing verification hunts for.
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.
- 8d ago First seen · 135 lines · 137 tokens per session scan A 5779ed855a52
evidence-ledger is a skill published in the GitHub repository synaptiai/synapti-marketplace (6 stars, last pushed yesterday), licensed Apache-2.0. It adds 137 tokens to every session and 2,855 once invoked, about $0.0007 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-09-03.
Other skills, from other repositories
create-or-update-concepts
Scan and analyze the project codebase to create or update concept files in agents-context/concepts/ (organized by domains/, source/, shared/) and update the README index and Load-When Cheatsheet.
step2-scope-tasks
Break a specification into ordered task groups with explicit context-awareness directives.
step1-write-spec
Gather requirements through structured Q&A, then formalize into a specification document.
create-pr
Creates a GitHub Pull Request on the current branch with a description focused on WHAT changed (not HOW). Uses emojis in the title and description. Use when the user asks to create a PR, open a pull request, or submit changes for review. Triggers on mentions of PR, pull request, merge request, or code review.
plan-product
Define product mission, vision, target users, and technology stack.
step4-archive-spec
Archive a completed spec — moves it to specs-archived and blocks agent access.