Loopy is a library and website of repeatable workflows that help AI agents learn from results and take the next useful step. It is for people and agents designing, finding, adapting, running, and reviewing structured agent workflows. Its catalogue add-ons provide an optional guided skill for working with the published loop collection.
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 skills add Forward-Future/loopy --skill loop-librarygit clone --depth 1 https://github.com/Forward-Future/loopyWrote 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/forward-future/loopy/loop-library)<a href="https://agentmods.dev/skills/forward-future/loopy/loop-library"><img src="https://agentmods.dev/badge/skills/forward-future/loopy/loop-library/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/forward-future/loopy/loop-library"><img src="https://agentmods.dev/badge/skills/forward-future/loopy/loop-library.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket pass
- Snyk warn
- NVIDIA SkillSpector pass
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.00065 | $0.03285 |
| Opus 5.5 | $0.00026 | $0.01314 |
| Sonnet 5.5 | $0.00013 | $0.00657 |
| Haiku 4.5 | $0.00006 | $0.00329 |
Grade A, and why
loop-library 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- loopy — 97% identical, 10 lines differ
How it starts
The opening of the file, as written. The whole thing — 306 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Loop Library (legacy alias)
loop-library is the compatibility name for Loopy. Complete the user's request
with this workflow. Use loopy, $loopy, or /loopy for new installations
and explicit invocations.
Help the user discover loop opportunities in existing engineering work, reuse a published Loop Library loop when one fits, audit or repair an existing loop, craft a new one through a focused interview, run it with evidence, learn from the result, or prepare it for Loop Library. Treat a loop as a feedback system with terminal states, not as permission for endless autonomy.
Route the request
Choose the smallest useful path:
- Discover: Analyze a codebase, coding-thread history, or both for repeated work that can become a bounded loop.
- Find: Recommend one to three published loops for a stated problem.
- Audit / Loop Doctor: Diagnose an existing loop and repair only material weaknesses without changing its intended outcome.
- Adapt: Start from a published loop and replace its thresholds, tools, cadence, owners, or checks without weakening its feedback cycle.
- Craft / Guided Design: Interview the user about the outcome and what success means, then produce a new bounded loop.
- Run: Execute an identified loop within the user's authorized scope and return an evidence-backed run receipt.
- Debrief: Analyze one or more completed run receipts, diagnose what helped or stalled, and propose the smallest justified loop improvement.
- Save / Reuse: On request, save a delivered loop to the project's
LOOPS.md, and reuse saved project loops when they fit a later request. - Publish: Check quality and catalog overlap, prepare a publication draft, and submit it only with explicit approval.
- Find, then craft: Search first. Use the nearest published loop as a scaffold and ask only about the missing decisions.
Do not ask for information the user already supplied. If an audit, run, debrief, or publication target is missing, ask the user to paste, link, or name it. For another vague request, begin with: "What are you trying to accomplish?"
What ships with it
6 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.
- 1mo ago First seen · 306 lines · 65 tokens per session scan A 5262b5a31b9f
loop-library is a skill published in the GitHub repository Forward-Future/loopy (3,183 stars, last pushed 1mo ago), licensed MIT. It adds 65 tokens to every session and 3,285 once invoked, about $0.0003 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 skills, from other repositories
agents-best-practices
Use this skill when designing, generating an MVP blueprint for, auditing, troubleshooting, refactoring, or explaining an agentic harness for any domain. Covers provider-neutral agent architecture for OpenAI, Anthropic, and OpenAI-compatible APIs: agent loops, tool design, record provenance, interactive presentation…
redpolicy-guide
An editorial policy for turning webinar transcripts into self-contained guides. A transcript is a written record of spoken material, while a self-contained guide can be understood without watching the webinar.
good-writing
A reference guide for writing clear, connected, well-structured text. It encourages explaining ideas like a colleague and removing wording that adds no value.
write-guide
A workflow for turning a webinar transcript into a written guide. It includes drafting the guide and reviewing the complete text for accuracy, clarity, style, and repeated content.
redpolicy-overview
A writing guide for research-based overview articles that explain concepts, approaches, markets, tool categories, or disputed topics. It covers dictionary-style, explanatory, and comparative articles.
write-overview
A workflow for researching and writing a review essay about a project topic when no finished source text exists. It gathers the facts, studies example essays when available and produces the article in a project output folder.