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/vivekparekh8/patch-receipt/patch-receiptnpx skills add vivekparekh8/patch-receipt --skill patch-receiptgit clone --depth 1 https://github.com/vivekparekh8/patch-receiptWrote 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/vivekparekh8/patch-receipt/patch-receipt)<a href="https://agentmods.dev/skills/vivekparekh8/patch-receipt/patch-receipt"><img src="https://agentmods.dev/badge/skills/vivekparekh8/patch-receipt/patch-receipt.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 | $0.00098 | $0.01015 |
| Opus 5 | $0.00049 | $0.00508 |
| Sonnet 5 | $0.00020 | $0.00203 |
| Haiku 4.5 | $0.00010 | $0.00102 |
Grade A, and why
patch-receipt 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 3d 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 — 48 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PatchReceipt
Create proof another reviewer can inspect and replay. Verify the behavior with the strongest existing project test, preserve source evidence, normalize the comparison, annotate the subject, verify hashes, and publish only after explicit confirmation.
Workflow
- Define one falsifiable claim before editing. State the separate expected before and after outcomes.
- Capture the real before state before the fix. If lost, recover it from the base revision or a separate worktree and disclose reconstruction.
- Match viewport/device, route/screen, seed data, interaction, locale, orientation, authentication/app state, and timing.
- Choose the evidence path:
- Existing PNG/JPEG/MP4: use
media. - Executable request/response semantics: use
http. - Web, Android, or iOS work: read references/verification.md, run the targeted native/project verification, and capture its checkpoints as PNG or MP4 for a
mediarecipe.
- Existing PNG/JPEG/MP4: use
- Read references/recipe-format.md before writing the final recipe. Do not move the recipe afterward; the receipt binds its path and hash.
- Run
patchreceipt doctor. Resolve missing required CLI tools before continuing. Do not auto-install or configure optional MCP, browser, emulator, simulator, SDK, or device tooling. - Generate evidence:
- Media or captured UI:
patchreceipt build <recipe.json> - Backend/API:
patchreceipt capture-http <recipe.json> - Backend/API secrets: provide only referenced
PATCHRECEIPT_SECRET_*names and explicitly list them with--allow-env.
- Media or captured UI:
- Run
patchreceipt verify <output-directory>. Treat behavioral assertions, CLI receipt integrity, and API assertion success as separate results. - Inspect PNGs at full size, representative video frames, the complete MP4 interaction, saved assertions, and redacted supplementary evidence. Confirm boxes surround only the claimed subject.
- Review all evidence for credentials, personal data, device ids, signed-in browser state, internal hosts, signing data, or unrelated content.
- Summarize the claim, behavioral result, recipe, receipt, and limitations. Read references/publishing.md only when publication is requested.
What ships with it
4 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.
- 3d ago First seen · 48 lines · 98 tokens per session scan A e9f658c15cf9
patch-receipt is a skill published in the GitHub repository vivekparekh8/patch-receipt (3 stars, last pushed 24d ago), licensed MIT. It adds 98 tokens to every session and 1,015 once invoked, about $0.0005 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-31.
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.
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.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…