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/vcz-gray/loophaus/helpgit clone --depth 1 https://github.com/vcz-Gray/loophausWrote 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/vcz-gray/loophaus/help)<a href="https://agentmods.dev/commands/vcz-gray/loophaus/help"><img src="https://agentmods.dev/badge/commands/vcz-gray/loophaus/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.00568 |
| Opus 5 | $0.00003 | $0.00284 |
| Sonnet 5 | $0.00001 | $0.00114 |
| Haiku 4.5 | $0.00001 | $0.00057 |
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 — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Loophaus Plugin Help
Please explain the following to the user:
What is Loop?
Loop implements the Ralph Wiggum technique — an iterative development methodology based on continuous AI loops, pioneered by Geoffrey Huntley.
Core concept:
while :; do
cat PROMPT.md | claude-code --continue
done
The same prompt is fed to Claude repeatedly. The "self-referential" aspect comes from Claude seeing its own previous work in the files and git history, not from feeding output back as input.
Each iteration:
- Claude receives the SAME prompt
- Works on the task, modifying files
- Tries to exit
- Stop hook intercepts and feeds the same prompt again
- Claude sees its previous work in the files
- Iteratively improves until completion
Available Commands
/loop [OPTIONS]
Start a loop in your current session.
Usage:
/loop "Refactor the cache layer" --max-iterations 20
/loop "Add tests" --completion-promise "TESTS COMPLETE"
Options:
--max-iterations <n>— Max iterations before auto-stop--completion-promise <text>— Promise phrase to signal completion
/loop-stop
Stop an active loop (removes the loop state file).
/loop-plan
Interactive interview that generates a PRD with right-sized stories, activates the loop, and starts implementing story by story.
Usage:
/loop-plan Add user authentication with JWT and login UI
/loop-pulse
Check the status of an active loop, including iteration count and story progress.
/loop-orchestrator
Multi-agent orchestration patterns for parallel work streams.
Available Skills (via Skill tool)
loophaus:ralph-interview— PRD generation + loop startloophaus:ralph-orchestrator— Multi-agent patternsloophaus:ralph-loop— Direct loop executionloophaus:cancel-ralph— Cancel active loop
Key Concepts
Completion Promises
To signal completion, Claude must output a <promise> tag:
<promise>TASK COMPLETE</promise>
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 · 97 lines · 7 tokens per session scan A fc7baa01ed64
help is a command published in the GitHub repository vcz-Gray/loophaus (23 stars, last pushed 4mo ago), licensed MIT. It adds 7 tokens to every session and 568 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-30.
Other commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.