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 instructions/wsauret/flywheel/claude-mdgit clone --depth 1 https://github.com/wsauret/flywheelWrote 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/instructions/wsauret/flywheel/claude-md)<a href="https://agentmods.dev/instructions/wsauret/flywheel/claude-md"><img src="https://agentmods.dev/badge/instructions/wsauret/flywheel/claude-md.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.02942 | $0.02942 |
| Opus 5 | $0.01471 | $0.01471 |
| Sonnet 5 | $0.00588 | $0.00588 |
| Haiku 4.5 | $0.00294 | $0.00294 |
Grade C, and why
flywheel CLAUDE.md 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 5d 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
- **Don't clean up before debugging.** `rm -rf` the sandbox and log in the next-run setup; the previous run's evidence is gone forever. How it starts
The opening of the file, as written. The whole thing — 163 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Flywheel — claude.md
This repo develops the Flywheel plugin for Claude Code and OpenCode. Source lives in flywheel/ (plugin contents); integration tests live in tests/integration/. Architectural philosophy: @docs/adrs/0001-skill-design-as-negotiation.md
Running integration tests
The end-to-end test (tests/integration/cases/03-pipeline-end-to-end.test.sh) drives the full /yolo autonomous flow against the real Anthropic API. Prerequisites:
ANTHROPIC_API_KEYsettmux,claude,jq,bunxon PATH- The plugin installed via
bash install_claude_code.sh < /dev/null(stdin redirected to skip the Context7 prompt)
A typical run takes 25–45 minutes. Cost: real API tokens.
# Reinstall plugin first if any plugin file changed
bash install_claude_code.sh < /dev/null 2>&1 | tail -3
# Run e2e test in background, capture output
bash tests/integration/cases/03-pipeline-end-to-end.test.sh \
> /tmp/yolo-test.log 2>&1; echo "TEST EXITED: $?" >> /tmp/yolo-test.log
Smaller tests:
00-plugin-loads.test.sh— palette discovery, no model call (~30s)01-fly-work-resumes.test.sh—workskill against seeded session (~1–3min)02-fly-plan-creates-spec.test.sh—planskill end-to-end (~3–10min)
Monitoring a long-running test
Don't sit and watch the log. Use the Monitor tool with a script that emits events on milestones, deadlocks, and silent stops. Skeleton:
last_log=0; last_prompt=0; last_log_time=$(date +%s); stall_warned=0
while true; do
now=$(date +%s)
# 1. Test progress: emit each new PASS/FAIL/INFO line
cur_log=$(wc -l < /tmp/yolo-test.log 2>/dev/null || echo 0)
if [ "$cur_log" -gt "$last_log" ]; then
tail -n $((cur_log - last_log)) /tmp/yolo-test.log \
| grep --line-buffered -E "^(PASS|FAIL|INFO|Summary|TEST EXITED):" || true
last_log=$cur_log
last_log_time=$now
stall_warned=0
fi
# 2. Deadlock detection: AskUserQuestion prompt visible in tmux
pane=$(tmux capture-pane -t flywheel-int-yolo -p 2>/dev/null || echo "")
prompt=$(echo "$pane" | grep -cE "Enter to select|Submit answers|Ready to submit" 2>/dev/null || echo 0)
if [ "$prompt" -gt 0 ] && [ "$last_prompt" -eq 0 ]; then
echo "DEADLOCK_DETECTED: AskUserQuestion in pane"
echo "$pane" | tail -12
fi
last_prompt=$prompt
# 3. Silent-stop detection: log idle >5min while test still running
log_idle=$((now - last_log_time))
if [ "$log_idle" -gt 300 ] && [ "$stall_warned" -eq 0 ] && [ "$last_log" -gt 0 ]; then
echo "STALL_DETECTED: log idle ${log_idle}s — agent may have silent-stopped"
echo "$pane" | tail -10
stall_warned=1
fi
# 4. Completion: break on test exit (Summary OR TEST EXITED)
if grep -q "^Summary:\|^TEST EXITED:" /tmp/yolo-test.log 2>/dev/null; then
grep "^Summary:\|^TEST EXITED:" /tmp/yolo-test.log | tail -3
break
fi
sleep 30
done
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.
- 5d ago First seen · 163 lines · 2,942 tokens per session scan C 9f3f56a6af4c
flywheel CLAUDE.md is an instructions file published in the GitHub repository wsauret/flywheel (14 stars, last pushed yesterday), licensed MIT. It adds 2,942 tokens to every session, about $0.0147 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other instructions, from other repositories
Codewhale AGENTS.md
AGENTS.md instructions for Hmbown/Codewhale, covering codewhale agent guidance, the ponytail method, working rules, landing other people's work and merging under a gate.
Codewhale CLAUDE.md
Claude Code instructions for Hmbown/Codewhale, a project described as: Open-source coding agent for your terminal, built in Rust and on a journey of continuous community improvement. Issues and PRs welcome.
Tianshu-harness CLAUDE.md
Claude Code instructions for huiliyi37/Tianshu-harness, covering 天枢 (tianshu) / rivet, build & test, architecture, conventions and known constraints.
zot AGENTS.md
AGENTS.md instructions for patriceckhart/zot, covering working agreement for zot, product intent, starting a task, code ownership map and correctness contracts.
pvetui AGENTS.md
AGENTS.md instructions for devnullvoid/pvetui, covering agent instructions, initial setup, development workflow, quick reference and code quality standards.
pvetui CLAUDE.md
Claude Code instructions for devnullvoid/pvetui: Canonical instructions live in AGENTS.md.