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 skills/sangrokjung/claude-forge/loop-forgenpx skills add sangrokjung/claude-forge --skill loop-forgegit clone --depth 1 https://github.com/sangrokjung/claude-forgeWrote 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/skills/sangrokjung/claude-forge/loop-forge)<a href="https://agentmods.dev/skills/sangrokjung/claude-forge/loop-forge"><img src="https://agentmods.dev/badge/skills/sangrokjung/claude-forge/loop-forge.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.1 | $0.00262 | $0.03649 |
| Opus 5 | $0.00131 | $0.01825 |
| Sonnet 5 | $0.00052 | $0.00730 |
| Haiku 4.5 | $0.00026 | $0.00365 |
Grade A, and why
loop-forge 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 2d 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 — 252 lines — stays where its author put it; the contents beside it link to each section on GitHub.
loop-forge — stamp a guarded, reusable loop (/loop-forge)
Picture an engraving shop. A customer who can't engrave walks in and just describes the seal they keep needing — "I want to do this over and over." The artisan ① recognizes which of 5 standard molds (loop shapes) it is, ② asks what letters to cut (the blanks), ③ cuts them into a proven mold, ④ automatically fits a "misprint detector" (the verifier) and an "out-of-ink stop" (the hardstop), ⑤ pulls one test impression to show the customer, and ⑥ once they approve, hands back a reusable
/commandthey can stamp again any time — the same in Claude Code and in any other agent via a paste-able prompt.
What this tool actually does
Someone who doesn't code can't author a reusable /command that makes an AI repeat
a task reliably. loop-forge closes that gap. It takes a vague one-liner and stamps
it into a reusable slash command, while automatically attaching the two safety
devices a non-developer doesn't even know to ask for:
- Verifier (maker ≠ checker) — the loop's output is re-checked in a pass that is separate from the pass that produced it, so the loop can't grade its own homework.
- Hardstop — a budget/count/cooldown ceiling, so a loop can't quietly break while burning tokens.
That auto-injection is the decisive difference from a plain prompt generator or a developer-facing skill builder.
Before → after (the elevator demo):
User: "I want to summarize 100 shop reviews into 3 lines each"
│
loop-forge:
1. Diagnoses → Batch loop
2. Interviews → where are the items? per-item task? where does output land? a cap?
3. Auto-injects → verifier (count in == count out + independent spot re-check)
+ hardstop (max_items budget + per-item fail cap + abort at 20% failure)
4. Previews → "here's how it will run" (+ optional 1-item sample)
5. Stamps → /review-summary (reusable forever; safety baked in)
When it triggers
/loopor/loop "<one-line situation>"(full command/loop-forge; alias/make-it-loop)- "automate this" / "make this repeatable" / "turn this into a command"
- "summarize all 100 reviews" / "do this for every item"
- "do X every time an email arrives" / "alert me when a condition is met"
- "generate a few options and pick the best one"
- any time you'd rather capture a recurring task as a reusable
/commandthan re-type the prompt by hand
What ships with it
26 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- references/archetypes/batch.md 8.2 KB
- references/archetypes/explore.md 9.6 KB
- references/archetypes/pipeline.md 8.8 KB
- references/archetypes/refine.md 8.9 KB
- references/archetypes/watch.md 14 KB
- references/assembler.md 9.6 KB
- references/classifier.md 7.5 KB
- references/codex-prompt-mechanism.md 8.8 KB
- references/interviewer.md 15 KB
- references/loop-spec-schema.md 7.4 KB
- references/renderers/claude-code.md 8.0 KB
- references/renderers/portable-prompt.md 11 KB
- tools/check_safety.py 4.3 KB runs code
- tools/classify_signals.py 5.3 KB runs code
- tools/corpus.jsonl 5.8 KB
- tools/examples/batch/claude-command.md 2.7 KB
- tools/examples/batch/portable-prompt.md 3.3 KB
- tools/examples/batch/spec.json 1.5 KB
- tools/examples/explore/spec.json 1.9 KB
- tools/examples/pipeline/spec.json 1.9 KB
- tools/examples/refine/spec.json 1.7 KB
- tools/examples/watch/spec.json 2.3 KB
- tools/loop_spec.schema.json 4.4 KB
- tools/smoke_e2e.sh 4.4 KB runs code
- tools/test_check_safety.py 958 B runs code
- tools/test_classify_signals.py 697 B runs code
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.
- 2d ago First seen · 252 lines · 262 tokens per session scan A 04b15d7986c0
loop-forge is a skill published in the GitHub repository sangrokjung/claude-forge (825 stars, last pushed 2d ago), licensed MIT. It adds 262 tokens to every session and 3,649 once invoked, about $0.0013 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-09-03.
Other skills, from other repositories
spec-driven-workflow
SPEC-First planning workflow - explore codebase, gather requirements, create execution plan through dialogue (read-only).
confirm-plan
Plan confirmation workflow - extract plan from conversation, create file, auto-review with Interactive Recovery. Use for confirming plans after /00plan.
setup-workflow
Initial setup workflow for claude-pilot plugin - directory creation, statusline configuration, documentation sync, GitHub star request.
close-plan
Plan completion workflow - archive plan, verify todos, create git commit, push with retry. Use for finalizing completed plans.
release
Plugin release workflow skill for version bumping, git tagging, and GitHub release creation. Use when releasing plugin versions with automated CHANGELOG generation and version synchronization.
git-master
Git workflow mastery - staging, committing, branching, PR creation. Apply conventional commits, Co-Authored-By attribution. Only create commits when user explicitly requests.