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/ksimback/looperWrote 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/ksimback/looper/looper)<a href="https://agentmods.dev/commands/ksimback/looper/looper"><img src="https://agentmods.dev/badge/commands/ksimback/looper/looper/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/ksimback/looper/looper"><img src="https://agentmods.dev/badge/commands/ksimback/looper/looper.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.00009 | $0.00361 |
| Opus 5.5 | $0.00004 | $0.00144 |
| Sonnet 5.5 | $0.00002 | $0.00072 |
| Haiku 4.5 | $0.00001 | $0.00036 |
Grade A, and why
looper 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
/looper
Run the Looper skill as an explicit slash command.
Arguments from the user: $ARGUMENTS
Resolve Looper
Find the Looper skill root before doing any loop-design work:
- Prefer the global Claude Code skill install:
- Windows:
%USERPROFILE%\.claude\skills\looper - macOS/Linux:
$HOME/.claude/skills/looper
- Windows:
- If that directory does not contain
SKILL.md, stop and tell the user to install Looper with the README instructions. - Read
SKILL.mdfrom that directory completely and follow its workflow exactly. Treat the located directory asCLAUDE_SKILL_DIRwhen running helper scripts.
Arguments
Parse $ARGUMENTS as [target-dir] [--template <name>], in any order:
- If
--templateis present, take the next token as the template name and follow the skill's Template Mode (the catalog lives attemplates/loops/inside the skill directory).--templatewith no name means: show the catalog and ask. - Remove
--template <name>from the arguments first; everything left is the target directory — treat it as a single path even if it contains spaces (e.g.C:\My Loops\out), and do not split it into multiple tokens. If nothing is left, use./looper-output.
Then continue with the Looper skill workflow.
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 · 40 lines · 0 tokens per session scan A 796d3fa37147
looper is a command published in the GitHub repository ksimback/looper (712 stars, last pushed 2mo ago), licensed MIT. It adds 9 tokens to every session and 361 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
research
Research a technical or product question.
build
Mini spec-first development workflow for well-scoped implementation tasks with human in the loop.
clean-check
Analyze code for cleanliness issues (unused code, comment quality, formatting, naming, complexity). Delegates to the code-cleanliness agent.
firebase-publish
Create or reuse a Firebase project, configure Hosting, and deploy the current static site. Never deletes.
cti-report
Render case deliverables — relationship graph (PNG/SVG/Mermaid) and a polished PDF/DOCX assessment. Usage: /cti-report [--graph|--pdf].
eval-merge
Use the Read tool to load .skill-compass/{skill-name}/manifest.json. Verify.