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 commands/ronronner02/codepilot-agent/spec-dogfoodgit clone --depth 1 https://github.com/ronronner02/codepilot-agentWrote 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/commands/ronronner02/codepilot-agent/spec-dogfood)<a href="https://agentmods.dev/commands/ronronner02/codepilot-agent/spec-dogfood"><img src="https://agentmods.dev/badge/commands/ronronner02/codepilot-agent/spec-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 | $0.00014 | $0.05241 |
| Opus 5 | $0.00007 | $0.02620 |
| Sonnet 5 | $0.00003 | $0.01048 |
| Haiku 4.5 | $0.00001 | $0.00524 |
Grade C, and why
spec-dogfood scanned grade C 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 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.
Tells the agent never to refusehighAnti-refusal
Suppressing the ability to decline removes a core safety control; a later harmful request then succeeds.
2. **Refuse to run on the trunk — branch/blank targets only.** If a *branch-name or blank* target resolves to the trunk (`main`/`master`/the detected default), stop — there is no diff to dogfood. A **PR is always diffabl How it starts
The opening of the file, as written. The whole thing — 244 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Command support root: .claude/spec-first/workflows/spec-dogfood. Treat it as the loaded skill directory whenever this inlined workflow refers to SKILL_DIR or the directory containing SKILL.md.
Dogfood
Act as a QA engineer who dogfoods the active branch end-to-end: understand every change, test every change in a real browser as a user would, and fix small breakages autonomously until the branch has a clear readiness verdict.
This is diff-scoped, not whole-app exploration. You test what this branch introduced or modified versus the trunk.
Workflow Contract Summary
When To Use
Use when a PR, branch, or current non-trunk branch needs autonomous browser dogfooding before review or shipping: changed-flow mapping, persona-aware journey testing, small fixes, regression tests, and a durable report.
When Not To Use
Do not use for collaborative UI polish (spec-polish), ordinary browser smoke tests (spec-test-browser when delegated), static code review (spec-code-review), implementation planning (spec-plan), broad whole-app exploration, or large product/architecture decisions.
Inputs
A PR number, branch name, or current branch; optional --port; git diff against trunk; project dev-server conventions; persona/strategy docs when present; browser observations and test results.
Outputs
Incrementally updated dogfood report under docs/dogfood-reports/, flowcharts, test matrix statuses, explicitly authorized small source fixes with regression evidence, blocked authorization/human-decision items, and a final readiness verdict.
Artifacts
docs/dogfood-reports/<YYYY-MM-DD>-<branch-slug>-dogfood.md, authorized source/test changes, commits only when separately requested, transient screenshots in OS temp, and optional reusable learnings handed to spec-compound.
Failure Modes
Trunk target with no diff, unsafe checkout or dirty working tree, missing agent-browser, missing or failing dev server, external-interaction flows needing human verification, ambiguous fixes requiring human product/architecture decisions, or failing automated suite after browser matrix completion.
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 · 244 lines · 14 tokens per session scan C 93634051f615
spec-dogfood is a command published in the GitHub repository ronronner02/codepilot-agent (0 stars, last pushed 3d ago), licensed MIT. It adds 14 tokens to every session and 5,241 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it C with 1 finding (tells the agent never to refuse). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
maggy
Start Maggy (the AI engineering command center) and open the dashboard in a browser.
Hexagonal.Gatekeeper
Your role is to perform a deep, architecture-focused code review on a specific branch. You must validate that all changes strictly follow Hexagonal Architecture (Ports & Adapters) principles and align with the existing codebase patterns.
Hexagonal.Refactor
Your task is to fix the reported issues in the current branch.
PyTest.GateKeeper
You are a Senior QA Automation Engineer with deep expertise in Python testing and the pytest framework.
OPSX: Verify
Verify implementation matches change artifacts before archiving.
OPSX: Archive
Archive a completed change in the experimental workflow.