Borrowing it
Nothing to install: this file belongs to NinjaScoutZ/houmi-mcp. 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/NinjaScoutZ/houmi-mcp/main/.agents/skills/loop/SKILL.mdgit clone --depth 1 https://github.com/NinjaScoutZ/houmi-mcpWrote 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/ninjascoutz/houmi-mcp/loop)<a href="https://agentmods.dev/skills/ninjascoutz/houmi-mcp/loop"><img src="https://agentmods.dev/badge/skills/ninjascoutz/houmi-mcp/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/skills/ninjascoutz/houmi-mcp/loop"><img src="https://agentmods.dev/badge/skills/ninjascoutz/houmi-mcp/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.00030 | $0.00469 |
| Opus 5.5 | $0.00012 | $0.00188 |
| Sonnet 5.5 | $0.00006 | $0.00094 |
| Haiku 4.5 | $0.00003 | $0.00047 |
Grade A, and why
loop 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
/loop — Autonomous Marathon
Continuous self-driving development cycle. Runs until all LEDGER cards are done or time limit is reached.
The Perpetual Cycle
┌─────────────────────────────────────────────────────────┐
│ 1. POP — houmi_ledger(action="pop_card") │
│ Get highest-priority open card from disk. │
└───────────────────────────┬─────────────────────────────┘
│
┌───────────────────────────▼─────────────────────────────┐
│ 2. EXECUTE — Write production code in frontend_rework/ │
│ Follow frontend-design + antigravity-design standards │
│ If backend function needed → houmi_backend_sync │
└───────────────────────────┬─────────────────────────────┘
│
┌───────────────────────────▼─────────────────────────────┐
│ 3. GRILL — houmi_stack_grill + adversarial self-check │
│ Attack: Type any? Canvas leaks? Hollow code? UX? │
│ If defects found → add new cards to LEDGER │
└───────────────────────────┬─────────────────────────────┘
│
┌───────────────────────────▼─────────────────────────────┐
│ 4. CLOSE — houmi_ledger(action="close_card") w/evidence │
│ Evidence = build output + grill results │
└───────────────────────────┬─────────────────────────────┘
│
┌───────────────────────────▼─────────────────────────────┐
│ 5. WAKE — schedule(DurationSeconds=2, Prompt= │
│ "LOOP PULSE: pop next card, execute, grill, close") │
│ Loop back to Step 1 immediately. │
└─────────────────────────────────────────────────────────┘
Termination
- All LEDGER cards closed + grill returns 0 critical issues.
- User sends
/stopor cancels the schedule task.
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 · 45 lines · 30 tokens per session scan A 7c57a9c0d520
loop is a skill published in the GitHub repository NinjaScoutZ/houmi-mcp (0 stars, last pushed 1mo ago), licensed MIT. It adds 30 tokens to every session and 469 once invoked, about $0.0001 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-31.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
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…
next-cache-components-optimizer
Optimize the meaningful UI available immediately from a Next.js route on an initial load (hard navigation) or named client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route and entry point at a time; the shipped test then guards…