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/jonyandunh/claude-code-watchdog/helpgit clone --depth 1 https://github.com/JonyanDunh/claude-code-watchdogWrote 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/jonyandunh/claude-code-watchdog/help)<a href="https://agentmods.dev/commands/jonyandunh/claude-code-watchdog/help"><img src="https://agentmods.dev/badge/commands/jonyandunh/claude-code-watchdog/help.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.00007 | $0.02379 |
| Opus 5 | $0.00003 | $0.01189 |
| Sonnet 5 | $0.00001 | $0.00476 |
| Haiku 4.5 | $0.00001 | $0.00238 |
Grade A, and why
help 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 4d 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 — 119 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Watchdog Plugin Help
Please explain the following to the user in clear, friendly language. Do not dump the markdown verbatim — synthesize and present it.
What is Watchdog?
Watchdog is a self-referential loop for Claude Code. You give it a prompt once, and it re-feeds that same prompt to Claude after every turn until the task genuinely stops producing file edits. The agent is not told a loop is running, so it cannot fake a completion signal to escape early.
Core mechanic:
- You run
/watchdog:start "<prompt>" [--max-iterations N] - Claude works on the task, modifying files
- Claude's turn ends — the Stop hook intercepts
- A headless Claude Haiku classifier inspects every tool invocation from that turn and decides: did any of them directly modify a project file?
- If yes → re-feed the original prompt as a new user turn, loop continues
- If no (or
--max-iterationsreached, or/watchdog:stopinvoked) → exit cleanly
The "self-reference" means each iteration sees the previous iteration's file edits and git state, so Claude builds on its own prior work without any external orchestrator.
Why the Haiku classifier?
Instead of a hard-coded tool-name whitelist (which misses Bash(sed -i …), MCP SQL writes, and other indirect mutations), Watchdog asks a headless Haiku instance to read every tool invocation's full input and judge semantically whether a project file was modified. The verdict is a single token: FILE_CHANGES or NO_FILE_CHANGES. Side effects that don't touch project files — running containers, remote DB writes, network calls — are correctly ignored.
Available commands
/watchdog:start "<PROMPT>" [--max-iterations N] [--exit-confirmations N] [--prompt-file <path>] [--watch-prompt-file] [--no-classifier]
Start a Watchdog in the current session.
Usage:
/watchdog:start "Refactor services/cache.ts to use the new API. Iterate until pnpm test:cache passes." --max-iterations 20
/watchdog:start "Add tests for auth.ts until coverage hits 80%."
/watchdog:start --prompt-file ./tmp/my-big-prompt.txt --max-iterations 20
/watchdog:start "Refactor cache.ts" --exit-confirmations 3 --max-iterations 20
/watchdog:start --prompt-file ./tmp/task.md --watch-prompt-file --max-iterations 20
/watchdog:start "Build until I /watchdog:stop" --no-classifier
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.
- 4d ago First seen · 119 lines · 7 tokens per session scan A 3d8ffcc4ba8a
help is a command published in the GitHub repository JonyanDunh/claude-code-watchdog (4 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 7 tokens to every session and 2,379 once invoked, about $0.0000 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 commands, from other repositories
init
Install the formatters this repository needs, with every command visible before it runs.
brand-generate
Generate an on-brand document from a saved Brand Profile.
genshijin-compress
Markdown・テキストファイルを原始人形式へ安全圧縮.
save
Save this conversation as a new or existing reusable context.
wp-polylang
Translate an existing WordPress site into a second language using Polylang.
standup
Show a daily standup summary with completed, in-progress, and blocked tasks across all active epics.