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.
git clone --depth 1 https://github.com/runnithan/claudex-setupWrote 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/runnithan/claudex-setup/claude-loop)<a href="https://agentmods.dev/commands/runnithan/claudex-setup/claude-loop"><img src="https://agentmods.dev/badge/commands/runnithan/claudex-setup/claude-loop/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/runnithan/claudex-setup/claude-loop"><img src="https://agentmods.dev/badge/commands/runnithan/claudex-setup/claude-loop.svg" alt="Reviewed on agentmods" width="80" 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.00072 | $0.07897 |
| Opus 5.5 | $0.00029 | $0.03159 |
| Sonnet 5.5 | $0.00014 | $0.01579 |
| Haiku 4.5 | $0.00007 | $0.00790 |
Grade B, and why
claude-loop scanned grade B 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 6d 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.
Unrestricted tool accessmediumExcessive agency
A wildcard tool grant or "run any command" leaves no least-privilege boundary at all.
or run any command that writes. Use Read, Grep, Glob and read-only git How it starts
The opening of the file, as written. The whole thing — 519 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/claude-loop: review, fix, repeat until clean
Review the codebase with an independent Claude reviewer, fix what it finds, and keep looping until the reviewer comes back clean twice in a row on everything in scope. Run autonomously. Do not report back between rounds and do not ask permission to continue; the owner starts it and walks away. This overrides any session protocol that asks for per-step approval or a per-task report (keep its evidence habits). Questions for the owner are collected as you go and asked once, in the §7 report.
After any compaction, re-read this whole file (a user-scope install lives
at ~/.claude/commands/claude-loop.md) and STATE.md before continuing.
Compaction keeps only the start of a long command.
This is /codex-loop with the reviewer swapped for a headless claude -p
session. It costs Anthropic usage instead of Codex usage. What it gives up is
the differently-trained reviewer, so every rule below about reviewer
independence exists to win back as much of that as possible.
Scope
- Repo mode, the default. The whole codebase as it stands at HEAD, one
area per round;
--scope PATH...limits it to those paths. In §0, split the tracked source into areas along directory lines, each roughly 3,000 to 8,000 lines of non-test source, ordered by risk (auth, payments, personal data and retention, migrations first). Tests are reviewed with the code they cover. Skip generated, vendored and lock files, fixtures, binary assets and docs. Stay on an area until it has two consecutive clean reviews, then move on. When every area is done, run the closing review: diff mode over the loop's own commits (<started>...HEAD) until two consecutive clean rounds, which catches a fix in one area that broke another. Skip it if the loop committed nothing. - Diff mode,
--base REF. Only what the current branch adds on top ofREF(a branch or a SHA), the right check before merging.REFis the comparison point, not the branch under review: run it from the feature branch.
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.
- 6d ago Changed · +29 lines 8e67f0c6db2d
- 7d ago First seen · 490 lines · 72 tokens per session scan B 5de29eb7dff0
claude-loop is a command published in the GitHub repository runnithan/claudex-setup (1 stars, last pushed 6d ago), licensed MIT. It adds 72 tokens to every session and 7,897 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it B with 1 finding (unrestricted tool access). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-10-04.
Other commands, from other repositories
review-skills
Review changed skills: automated bash checks + 9 structural dimensions (D1-D9) + 5 intent checks (M1-M5). PASS/FAIL verdict. Fix in-place.
verify
A verification command that runs a test agent and a code-review agent in the same round, then combines their results.
octo-deliver
"Delivery phase - Review, validate, and test with multi-AI quality assurance".
test
Run the repository's actual test suite: every ecosystem's canonical runner — NOT run is never green.
ia-verify
Run pre-PR verification chain: build, types, lint, tests, security scan, diff review.
record
Record a browser walkthrough of a URL using Antigravity (agy). Generates .webm video, screenshots, and a report. Auto-converts to MP4 if ffmpeg is available.