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/ivy00johns/skill-madness/loop-controllernpx skills add ivy00johns/Skill-Madness --skill loop-controllergit clone --depth 1 https://github.com/ivy00johns/Skill-MadnessWhat 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.00185 | $0.05384 |
| Opus 5 | $0.00093 | $0.02692 |
| Sonnet 5 | $0.00037 | $0.01077 |
| Haiku 4.5 | $0.00018 | $0.00538 |
Grade A, and why
loop-controller 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 — 349 lines — stays where its author put it; the contents beside it link to each section on GitHub.
loop-controller
Why this is a deliberate (
disable-model-invocation) skill. A loop edits, commits, and spends tokens on its own. You want to type/loop-controller(or have the orchestrator dispatch it), not have Claude silently start an autonomous loop because a test happened to fail. The discipline below is what makes that safe.
The one rule that governs every loop
A loop is only as good as its stopping condition. Loops converge when "done" is an external signal the agent cannot argue with — a test exit code, a coverage percentage, an empty queue, a fresh evaluator's verdict. They diverge — oscillate, thrash, or run the budget to zero — when "done" is a subjective judgment the agent grades itself on. Agents are pathological optimists about their own work; left to self-assess, they declare victory early.
There is a subtler failure an objective proof does not cure: a signal that is mechanical, default-FAIL, and un-gameable can still measure the wrong thing. A test suite green against a mock, a stub, or a fixture is all three of those — and proves nothing about whether the real product works. That is convergence on a fiction, and because it wears the costume of rigor (an exit code! a number!) it slips past review more easily than a subjective claim would. 65 green tests against a mocked backend look exactly like 65 green tests against the real one. So the proof must measure the real goal, not a stand-in for it (Step 2) — un-gameable and pointed at the thing that actually matters.
So the entire job of this skill is to turn a fuzzy "keep working on X" into a convergent loop: a mechanical proof of the real goal, the right execution primitive, and a guardrail stack that stops the loop whether or not the proof is ever met.
Everything else here — fix-until-green, coverage-loop, perf-loop — is a config of this harness: a specific proof plugged into the same machinery. Author new loops against this skill; don't reinvent the loop engine.
What ships with it
3 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.
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 · 349 lines · 185 tokens per session scan A 878cebccd26f
loop-controller is a skill published in the GitHub repository ivy00johns/Skill-Madness (11 stars, last pushed 22d ago), licensed MIT. It adds 185 tokens to every session and 5,384 once invoked, about $0.0009 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…