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/attckdigital/smith/smith-ledgernpx skills add ATTCKDigital/smith --skill smith-ledgergit clone --depth 1 https://github.com/ATTCKDigital/smithWhat 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.00059 | $0.05524 |
| Opus 5 | $0.00030 | $0.02762 |
| Sonnet 5 | $0.00012 | $0.01105 |
| Haiku 4.5 | $0.00006 | $0.00552 |
Grade A, and why
smith-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.
How it starts
The opening of the file, as written. The whole thing — 549 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Smith Ledger — Knowledge Base Management
Browse, search, and manage the Smith Ledger. The Ledger is the persistent knowledge base that captures patterns, antipatterns, tool preferences, edge cases, and project quirks learned from past Smith workflows. It lives at .smith/vault/ledger/.
Arguments: $ARGUMENTS
Vault Logging
Throughout this action, log significant events to the vault session log. Read the session log path from .smith/vault/.current-session. If the file is missing or the vault is not initialized, skip all logging silently.
Append entries using this format:
### [HH:MM:SS] /smith-ledger <event>
**User Request:**
> <verbatim user message that triggered this action>
**Subcommand:** <dashboard|list|show|search|prune|promote|demote|export|reset>
**Synthesized Input:** <brief summary of args/filters>
**Outcome:** <what happened — counts, changes made, results found>
**Artifacts:** <files read/modified>
**Systems affected:** <system IDs>
Log at these points:
- On invocation — which subcommand was used and with what arguments
- After any mutation — prune, promote, demote, or reset operations that modify Ledger files
Ledger Directory Structure
The Ledger lives at .smith/vault/ledger/ with the following files:
.smith/vault/ledger/
meta.yaml # Overview stats — last reflection date, total counts, config
patterns.md # Validated approaches that work well
antipatterns.md # Approaches that failed or caused problems
tool-preferences.md # Tool/library/API usage preferences and gotchas
edge-cases.md # Non-obvious behaviors, boundary conditions, quirks in tools/APIs
project-quirks.md # Project-specific conventions, workarounds, and constraints
archive/ # Archived Ledger snapshots from resets
Ledger Entry Format
Each Ledger file (patterns.md, antipatterns.md, etc.) contains entries in this format:
## <Title>
- **Date:** YYYY-MM-DD
- **Category:** implementation | testing | debugging | specification | audit
- **Confidence:** low | medium | high
- **Observations:** N
- **Source reflections:** <comma-separated list of reflection session dates or spec IDs>
### Context
<When and why this pattern/antipattern/preference/edge-case applies>
### Pattern
<The actual pattern, antipattern, tool preference, edge case, or project quirk — what to do or what to avoid>
### Evidence
<Specific examples from past workflows that support this entry>
### Related
<Links to related entries, specs, or code files>
---
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 · 549 lines · 59 tokens per session scan A b2ee5d12c7aa
smith-ledger is a skill published in the GitHub repository ATTCKDigital/smith (52 stars, last pushed 1mo ago), licensed MIT. It adds 59 tokens to every session and 5,524 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.