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 tomascupr/sous-chef --skill receiptsgit clone --depth 1 https://github.com/tomascupr/sous-chefWrote 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/tomascupr/sous-chef/receipts)<a href="https://agentmods.dev/skills/tomascupr/sous-chef/receipts"><img src="https://agentmods.dev/badge/skills/tomascupr/sous-chef/receipts/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/tomascupr/sous-chef/receipts"><img src="https://agentmods.dev/badge/skills/tomascupr/sous-chef/receipts.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.00083 | $0.00427 |
| Opus 5 | $0.00042 | $0.00214 |
| Sonnet 5 | $0.00017 | $0.00085 |
| Haiku 4.5 | $0.00008 | $0.00043 |
Grade A, and why
receipts 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.
What it actually says
Receipts - print the check
Receipts are per-run cost artifacts written by serve and simmer into the current
repo at .sous-chef/receipts/<utc-timestamp>.md (ignored via
.git/info/exclude, never committed). Each holds the run's measured numbers and
ends with a shareable one-liner. The global ledger (~/.sous-chef/ledger.jsonl)
stays the cross-repo running tab; receipts are the per-run, per-repo story.
Printing the check
Read the last 10 receipts by filename (newest last) and render one table:
| when | task | worker | tokens | ~cost | ~saved vs Fable list | verdict |
Close with one line - "last N runs: ~$X of worker spend, ~$Y saved vs same-token Fable list." Sum only lines that exist; a receipt missing a number contributes nothing to that column - say so rather than papering over it.
If the user wants to share one, print that receipt's quoted summary verbatim - it is written to be pasted unedited.
No .sous-chef/receipts/ here? Say so - receipts appear after the first serve
or simmer in this repo (a bare fire tabs the ledger, not receipts).
The files behind it
- references/receipt-template.md - the format serve and simmer write, and the honesty rules every number follows.
- references/prices.md - the rough price table (API list, dated); edit it when list prices move.
What ships with it
2 files 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.
- 9d ago First seen · 36 lines · 83 tokens per session scan A c68e4dc2cff0
receipts is a skill published in the GitHub repository tomascupr/sous-chef (76 stars, last pushed 1mo ago), licensed MIT. It adds 83 tokens to every session and 427 once invoked, about $0.0004 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
b3os-report
A team reporting skill that turns approved markdown and HTML reports into entries in an internal reports portal. HTML becomes the main view when available, while markdown remains the source and download version.
b3os-ai-code-safety
As code and logic grow, the cost is not the happy path — it is coupling: a change ripples into places you did not touch, and a "small fix" breaks something unrelated. This skill is a code-structure and refactoring guide: structure well from the initial design so a change stays local, apply operational safety where…
b3os-team-inbox
A team message-bus client for sending, receiving, and recalling messages between AI teammates. It also supports replying to a specific message thread and sending final reports to the team lead.
b3os-team-member-lifecycle
Use when adding, testing, disabling, offboarding, or archiving a b3rys team member across Claude Code channel, OpenClaw, Hermes Agent, or future runtimes.
b3os
An onboarding workflow for b3os, a local system for creating and managing a team of AI agents.
b3os-task-loop
A task-tracking work loop that keeps individual, scheduled, and waiting tasks moving until they are completed, blocked, or awaiting approval.