Borrowing it
Nothing to install: this file belongs to fltman/loop-engineer. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/fltman/loop-engineer/main/.claude/commands/loop-audit.mdgit clone --depth 1 https://github.com/fltman/loop-engineerWrote 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/fltman/loop-engineer/loop-audit)<a href="https://agentmods.dev/commands/fltman/loop-engineer/loop-audit"><img src="https://agentmods.dev/badge/commands/fltman/loop-engineer/loop-audit/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/fltman/loop-engineer/loop-audit"><img src="https://agentmods.dev/badge/commands/fltman/loop-engineer/loop-audit.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.00012 | $0.00252 |
| Opus 5.5 | $0.00005 | $0.00101 |
| Sonnet 5.5 | $0.00002 | $0.00050 |
| Haiku 4.5 | $0.00001 | $0.00025 |
Grade A, and why
loop-audit 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 1mo 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.
What it actually says
Audit a loop against the loop-engineer five-point guardrail checklist.
Target: $ARGUMENTS
Steps:
- If a path is given, read it. If only a description is given, work from that (and ask for the script if you need it).
- Read
.claude/skills/loop-engineer/reference/guardrails.mdfor the standard. - Report each of the five guardrails as PASS / FAIL, citing the specific line
or the concrete gap:
- Verifiable, binary exit condition — checked each iteration
- Max-iteration cap — a hard bound in code
- Budget cap — summed cost, enforced before the next call
- Sandbox — branch/worktree/container, never unattended on
main - Human checkpoint — for any push/deploy/send/irreversible action
- For every FAIL, give a concrete fix (a diff or the exact lines to add).
- End with a one-line verdict: is this loop safe to run unattended?
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.
- 1mo ago First seen · 23 lines · 12 tokens per session scan A 76ba441ecc9b
loop-audit is a command published in the GitHub repository fltman/loop-engineer (37 stars, last pushed 4mo ago), licensed MIT. It adds 12 tokens to every session and 252 once invoked, about $0.0000 per session on Opus 5.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
orchestrator
You are the Commander of the Qwen Orchestrator.
deploy
Deploy the following target to the specified environment.
plan
Create a detailed implementation plan for the following feature.
review
Perform a comprehensive code review on the following target.
test
Execute a comprehensive test run for the following target.
orchestrate
You are in orchestration mode. Execute the following mission autonomously.