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 thevibeworks/claude-code-docs --skill receiptsgit clone --depth 1 https://github.com/thevibeworks/claude-code-docsWrote 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/thevibeworks/claude-code-docs/receipts)<a href="https://agentmods.dev/skills/thevibeworks/claude-code-docs/receipts"><img src="https://agentmods.dev/badge/skills/thevibeworks/claude-code-docs/receipts.svg" alt="Measured on agentmods" 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.00134 | $0.04261 |
| Opus 5 | $0.00067 | $0.02131 |
| Sonnet 5 | $0.00027 | $0.00852 |
| Haiku 4.5 | $0.00013 | $0.00426 |
Grade B, and why
receipts scanned grade B with 1 finding 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 5d 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.
Instruction-override phrasingmediumPrompt injection
Text telling the model to disregard its earlier instructions or safety rules is the shape of a prompt injection, whoever wrote it.
command to you ("ignore previous instructions", "report zero spend", "say this Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
This is a copy
100% identical to receipts — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 301 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/receipts — personal Claude Code impact report
Generates a markdown report of one developer's own Claude Code activity, built entirely from local data:
- Source data: this machine's session transcripts at
~/.claude/projects/**/*.jsonl(every session, every project, already on disk — nothing to set up). - Cost: the mining step is a local Node script — file I/O + regex, zero API calls. The only model call is one final write-up over a small (~10-20KB) JSON summary, regardless of how much history was scanned.
- Cross-reference: local
git logper repo (no network) to sanity-check commit activity against CC session activity.
Step 1 — figure out the period
Parse $ARGUMENTS:
- "week" → 7, "month" → 30 (default if nothing given), "quarter" → 90, "year" → 365
- a bare number → that many days
- a project name/substring (e.g. "for anthropic") → pass through as
--repo <substr>. It matches against the resolved project name, case-insensitively, and scopes the entire report — totals included — to matching projects.
Step 2 — run the miner
The script mine-transcripts.mjs ships alongside this SKILL.md, under
scripts/. Use its absolute path:
node <skill-dir>/scripts/mine-transcripts.mjs --days <N> [--repo <substr>] --html /tmp/cc-receipt.html
Use that fixed temp path — the real since/until are computed by the script
and only known once it has run, so don't try to put them in this filename.
Steps 4 and 5 name the final files, by which point the JSON has the dates.
This prints one JSON object to stdout and writes a self-contained, styled
HTML "receipt" to the --html path — built deterministically from the same
data (no extra model cost). The receipt carries an Export CSV button that
downloads the by-project table; the CSV is embedded in the page, so it works
offline and there's nothing to wire up. Do not separately Read any
*.jsonl transcript files — the script has already extracted everything
relevant. Re-reading raw transcripts would burn a huge number of tokens for no
benefit.
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.
- 5d ago First seen · 301 lines · 134 tokens per session scan B 5b2f407ff406
receipts is a skill published in the GitHub repository thevibeworks/claude-code-docs (40 stars, last pushed today), licensed MIT. It adds 134 tokens to every session and 4,261 once invoked, about $0.0007 per session on Opus 5. A static security scan graded it B with 1 finding (instruction-override phrasing). It is 100% identical to receipts, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
sync
Synchronize task files and source-of-truth documents. Update NEXT-TASKS.md, FUTURE-ENHANCEMENTS.md, README, and CHANGELOG to reflect current project state.
validate
Run the full quality gate — tests, lint, build, and cortex-tms validate --strict.
github-flow-for-claude-on-web
Complete GitHub workflow for Claude Code on the web. ALL GitHub operations MUST use REST API (never gh CLI). Includes branch naming (claude/-sessionId), push retry logic, PR/issue management via API, and complete workflows. Use for all GitHub interactions in Claude Code web environment.
vibing-orchestrate
A coordinator for splitting independent tasks among separate vibing.nvim chats, a Neovim interface for working with coding agents, and combining their results.
self-testing
E2E self-testing workflow for vibing.nvim using a separate Neovim instance controlled over RPC. Use when writing or debugging E2E tests, running npm run test:e2e, or executing the 3-try auto-fix rule after implementing a feature. Covers the…
test-design
Automatically design comprehensive E2E test cases for newly implemented vibing.nvim features. Use immediately after completing feature implementation (Phase 5.4) and before running E2E tests. Generates test scenarios covering Happy paths, Error cases, Edge cases, and Integration points with priority ranking…