Borrowing it
Nothing to install: this file belongs to boykush/scraps. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/boykush/scraps/main/.agents/skills/dogfood/SKILL.mdgit clone --depth 1 https://github.com/boykush/scrapsWrote 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/boykush/scraps/dogfood)<a href="https://agentmods.dev/skills/boykush/scraps/dogfood"><img src="https://agentmods.dev/badge/skills/boykush/scraps/dogfood/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/boykush/scraps/dogfood"><img src="https://agentmods.dev/badge/skills/boykush/scraps/dogfood.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.00127 | $0.01198 |
| Opus 5.5 | $0.00051 | $0.00479 |
| Sonnet 5.5 | $0.00025 | $0.00240 |
| Haiku 4.5 | $0.00013 | $0.00120 |
Grade A, and why
dogfood 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 7d 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 — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dogfood
The repository owner runs Scraps as a remote MCP server over their own wiki and uses it every day. Each request leaves a span. This skill reads those spans, finds where the tools and the way agents are told to use them fall short, and ships one improvement.
Only the owner can run it. The jaeger MCP server authenticates as them, and no one else gets past its login. This skill is also the only place in the repository that calls mcp__jaeger__*: outside it, leave those tools alone.
If the jaeger tools are missing or refuse the call, stop and say so. The package's README (apm_modules/boykush/ai-plugins/plugins/jaeger-remote-mcp/README.md) says how to sign in and when the cluster is down. Don't route around the login.
1. Read the traces
- Find the service with the services tool rather than assuming its name: it is the one whose spans come from the
scrapsinstrumentation scope. - Take the whole retention window unless the owner names another. A week of personal use is a small sample, so narrowing it further leaves little to read.
src/mcp/traced.rsowns what a span is named and which attributes it carries. Read it before interpreting them, since it changes as the telemetry improves.- A trace can hold other services' spans for the same request, such as a gateway in front. Count only the spans whose resource is the Scraps service, or each call is counted twice.
2. Find what the usage says
Set the calls beside what the server offers: src/mcp/server.rs for the tools, their descriptions and the server instructions, src/mcp/tools/ for each request schema.
- Tools never called. A tool nobody reaches for is either unneeded for this kind of use or undiscoverable from where agents stand when they would want it.
- Arguments that fight the schema. A default passed explicitly every time, an optional parameter never used, a value retried in another form.
- Sequences. What follows what, and where a sequence ends early. A search with no read after it is a question the response could not answer.
- Errors, and whether the message told the caller what to do next.
- Latency that every tool shares, as opposed to one tool's own.
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.
- 7d ago First seen · 69 lines · 127 tokens per session scan A 812d8898ae58
dogfood is a skill published in the GitHub repository boykush/scraps (45 stars, last pushed today), licensed MIT. It adds 127 tokens to every session and 1,198 once invoked, about $0.0005 per session on Opus 5.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-10-11.
Other skills, from other repositories
remem
Use when the user asks Codex to recall prior project context, save durable decisions or bug fixes, inspect remem memory health, or activate remem automatic memory hooks from the Codex plugin.
rust-check
Run cargo check on the current Rust project to find compile errors.
debug
Reproduce, minimize, localize, identify root cause, and distinguish diagnosis from an authorized fix. Prefer root-cause over symptom patches.
feedback
Skill "feedback" from Hmbown/Codewhale, covering feedback, when to use, setup, workflow and non-goals.
llmwiki
Build and use a persistent, citation-traceable knowledge wiki from documents, research papers, notes, or project documentation. Use for llmwiki projects, retrieving reusable evidence for an agent task, or compiling a corpus for repeated questions. A one-off file read or live web search does not need a wiki.
ast-grep
Use for ast-grep project setup, rule authoring, rule debugging, and structural search workflows.