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/beefiker/superloopy/superloopy-loopnpx skills add beefiker/superloopy --skill superloopy-loopgit clone --depth 1 https://github.com/beefiker/superloopyWhat 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.00031 | $0.05266 |
| Opus 5 | $0.00015 | $0.02633 |
| Sonnet 5 | $0.00006 | $0.01053 |
| Haiku 4.5 | $0.00003 | $0.00527 |
Grade A, and why
superloopy-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 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 — 228 lines — stays where its author put it; the contents beside it link to each section on GitHub.
superloopy-loop
Use this skill when the user asks for Superloopy, loopywork, lpy, a loop harness, durable criteria, evidence-backed completion, strict-but-light task flow, or guided next actions.
Contract
- State lives in
.superloopy/, or.superloopy/sessions/<id>/when--session-idis used. - Do not hand-edit
.superloopy/goals.json; use the CLI. - A criterion can pass only after a real artifact exists under the active evidence root.
- User steering must use
SUPERLOOPY_STEERJSON; do not hand-edit.superloopy/goals.json. - Executor receipts should end with
SUPERLOOPY_EVIDENCE: <path-under-active-evidence-root>. - Legacy
EVIDENCE_RECORDEDreceipts remain accepted for compatibility. - Tests are useful evidence, but completion requires the Superloopy evidence artifact.
- Use
superloopy loop provewhen an active goal needs command-backed evidence for its next unresolved criterion. - Keep the workflow lightweight unless the task genuinely needs heavier review.
- A leading
loopykeyword wakes the loop engineer: take the rest of the prompt as the brief, run the loop yourself, and report progress instead of asking the user to type Superloopy commands. loopywork,$lpy, andlpyare lighter prompt triggers; they inject guidance but never mutate.superloopy/state by themselves.- Full Loopy runs default to direct, concise, complete user-facing progress and final responses. Exact
say-it-straight off/직설 모드 끄기andsay-it-straight on/직설 모드 켜기controls apply only to the current incomplete loop; new loops reset this default to enabled. - This output overlay changes wording only. It never silently rewrites supplied prose, task artifacts, code, documentation, comments, evidence, quotations, or user source text; direct artifact editing remains explicit-only.
i-have-adhdstill owns structure, andhumanize-koreanstill owns Korean artifact rewriting.
Loop engineer (loopy keyword)
When the user opens a message with loopy <task>, act as the loop engineer:
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 · 228 lines · 31 tokens per session scan A 477c5e1cb603
superloopy-loop is a skill published in the GitHub repository beefiker/superloopy (108 stars, last pushed 8d ago), licensed MIT. It adds 31 tokens to every session and 5,266 once invoked, about $0.0002 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
watch
File sentinel that monitors the working directory for changes and marker comments, then auto-triggers appropriate skills. Poll-based via git diff against the last scan commit. Writes intake items for batch processing and routes marker actions through /do. Use for automatic reactions to file changes; do NOT use for…
infra-audit
Reads docker-compose, env files, ORM configs, and connection strings to map current infrastructure. Flags missing layers (cache, queue, analytics) based on observed access patterns. Outputs a structured infrastructure manifest.
scaffold
Project-aware file generation. Reads existing codebase conventions (naming, structure, imports, exports, test patterns) then generates new files that match exactly. Wires generated files into the project's registration points.
design
Generates and maintains a design manifest for visual consistency. In existing projects, reads current styles and documents the design language. In new projects, asks a few questions and generates a starter manifest. The post-edit hook reads the manifest and flags deviations.
live-preview
Mid-build visual verification loop. Takes screenshots of components during construction, not just after. Catches visual regressions and invisible features before they compound. Requires Playwright or similar screenshot tool.
marshal
Meta-orchestrator that takes any direction — broad, specific, or vague — and autonomously chains skills and context into actionable work. Gathers context from codebase, docs, and memory. Only asks the user when it genuinely cannot proceed. Single-session orchestrator.