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 agentmods add skills/lestrrat-ai/claude-code-plugins/ledgernpx skills add lestrrat-ai/claude-code-plugins --skill ledgergit clone --depth 1 https://github.com/lestrrat-ai/claude-code-pluginsWhat 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 | $0.00050 | $0.00438 |
| Opus 5 | $0.00025 | $0.00219 |
| Sonnet 5 | $0.00010 | $0.00088 |
| Haiku 4.5 | $0.00005 | $0.00044 |
Grade A, and why
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 2d 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
Ledger
Invocation: Claude Code /gauntlet:ledger; Codex $gauntlet:ledger.
-
Resolve repository root to an absolute path from the user-supplied checkout or current repository.
-
Resolve
../campaign/scripts/ledger.pyfrom this activeSKILL.mdto an absolute path. NEVER use a plugin-root environment variable. -
Select state file:
- User named a run, or current campaign context supplies one → use that run's
<repo>/.gauntlet/tmp/<run-id>/state.jsonl. - No run is known → enumerate
<repo>/.gauntlet/tmp/*/state.jsonlwithout reading the files. - Exactly one match → use it.
- No matches → report that no campaign ledger exists.
- Multiple matches → list run directory names and ask user to choose. NEVER guess by age or contents.
- User named a run, or current campaign context supplies one → use that run's
-
Run this argument vector with absolute paths:
["python3", "<absolute-ledger.py>", "--file", "<absolute-state.jsonl>", "table"] -
Append
"--all"only when user asks for hidden, merged, aborted, closed, or all entries. -
Print script stdout as-is — every line the script printed, adding none and removing none. That includes every
#line. The#lines below the grid disclose that the view is filtered and are always printed; the# <field>: <value>run-config block above it is printed only when the run'sstatus_verbositysetting selects it, so its absence is the tool's output, never something to restore. On failure, relay stderr as-is and stop.
Read-only. NEVER create, edit, parse, summarize, or reformat ledger data or table output.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2d ago First seen · 34 lines · 50 tokens per session scan A 8035d3b6a493
ledger is a skill published in the GitHub repository lestrrat-ai/claude-code-plugins (18 stars, last pushed 3d ago), licensed MIT. It adds 50 tokens to every session and 438 once invoked, about $0.0003 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.