Borrowing it
Nothing to install: this file belongs to fold-run/fold. 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/fold-run/fold/main/.claude/skills/dogfood/SKILL.mdgit clone --depth 1 https://github.com/fold-run/foldWrote 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/fold-run/fold/dogfood)<a href="https://agentmods.dev/skills/fold-run/fold/dogfood"><img src="https://agentmods.dev/badge/skills/fold-run/fold/dogfood.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.00069 | $0.00847 |
| Opus 5 | $0.00034 | $0.00424 |
| Sonnet 5 | $0.00014 | $0.00169 |
| Haiku 4.5 | $0.00007 | $0.00085 |
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 8d 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 — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Running fold and using it
fold's central claim is about what a client experiences, and the fastest way to check a claim about experience is to have the experience.
make dev-up # everything-server on :8098, fold on :8099
make dev-status # the health body, upstream by upstream
make dev-down
scripts/dev-stack.sh builds fold from the working tree, so it serves the
code you are editing. The upstream is the reference everything-server — the
same peer make conformance fronts, so what you see here and what CI gates
on are the same server. It is federated under the namespace demo rather
than passthrough, deliberately: namespacing is the behavior most worth
seeing from the outside (demo__echo, not echo).
Ports are overridable and are not the gateway's own default 8080, which is a popular squat — Docker Desktop takes it. The script refuses to start on a busy port and names the process holding it rather than failing obscurely.
Two clients
The Inspector — one method, scriptable, no session state to reason
about. /mcp-inspector covers it, including the invisibility diff: the same
method against fold and against the upstream directly, compared.
This Claude Code session — .mcp.json at the repo root points at
http://127.0.0.1:8099/mcp, so with the stack up and the server approved,
the session's own tool list contains fold's federated tools. That is a
genuine end-to-end client, with all the awkwardness a real one has.
The gateway must already be running: fold serves streamable HTTP and has no
downstream stdio mode, so nothing here is self-starting. If the server shows
as failed, the stack is down — make dev-up, then reconnect.
What to look at once it is up
- Namespacing round-trip. Tools list as
demo__*; a call with the namespaced name reaches the upstream under its bare name. A call with the bare name answers-31043. - The console at
http://127.0.0.1:8099/console/— the federation view an operator gets, served from the vendored assets (/console-sync). - Health, which answers 503 with a body when an upstream is down. Stop the upstream and watch the breaker move; "listening" and "ready" are different claims and this is where the difference is visible.
- The audit trail on stdout in
$TMPDIR/fold-dev-stack/fold.log— one event per terminal response, denials included.
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.
- 8d ago First seen · 70 lines · 69 tokens per session scan A 5c07d798b2c4
dogfood is a skill published in the GitHub repository fold-run/fold (1 stars, last pushed yesterday), licensed Apache-2.0. It adds 69 tokens to every session and 847 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-31.
Other skills, from other repositories
config-loader-helper
Diagnose configuration-related failures, enumerate required env vars, and guide safe local test setup (no secrets).
fix-suggester
Diagnose failures and propose minimal, test-backed fixes with verification and rollback instructions.
pinchtab-dev
Develop and contribute to the PinchTab project. Use when working on PinchTab source code, adding features, fixing bugs, running tests, or preparing PRs. Triggers on "work on pinchtab", "pinchtab development", "contribute to pinchtab", "fix pinchtab bug", "add pinchtab feature".
code-guidelines-go
Go 1.24–1.27 coding guidelines for the dimetron/pi-go AI agent runtime. Use this skill whenever writing, reviewing, or refactoring ANY Go code in pi-go. This covers idiomatic style, error handling, concurrency, project layout, testing (table-driven, fuzz, benchmarks, synctest), new stdlib usage, golangci-lint v2…
go-127
What changed in Go 1.27 (released August 2026) and how it changes the way Go is written in pi-go. Use this skill when writing or reviewing Go that could use a 1.27 feature, when bumping the go directive in go.mod, when a build or test behaves differently after a toolchain upgrade, or when code-guidelines-go points…
bubbletea-testing
Use this skill whenever writing tests for Bubble Tea (charmbracelet/bubbletea) TUI applications in Go. Triggers include any mention of testing Bubble Tea models, teatest, golden file testing for TUIs, testing tea.Cmd or tea.Msg, snapshot testing terminal output, or writing tests for any Go CLI/TUI that uses the Elm…