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 instructions/forward-future/loopy/agents-mdgit clone --depth 1 https://github.com/Forward-Future/loopyWhat 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.02320 | $0.02320 |
| Opus 5 | $0.01160 | $0.01160 |
| Sonnet 5 | $0.00464 | $0.00464 |
| Haiku 4.5 | $0.00232 | $0.00232 |
Grade A, and why
loopy AGENTS.md scanned grade A with 1 finding 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 yesterday.
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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -sS "https://here.now/api/v1/publishes/{slug}/data/suggestions?limit=50" \ How it starts
The opening of the file, as written. The whole thing — 202 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Loopy Repository Operating Rules
This repository holds two separate but related parts:
- Loop Library website — the public catalog (site shell, database, and
rendering). All website code lives under
loop-library/(loop-library/site/,loop-library/worker/,loop-library/scripts/,loop-library/audits/). - Loopy skill — the installable agent skill in
skills/loopy/, with the compatibility alias inskills/loop-library/.
The operating rules below govern the Loop Library website unless they call out
the skill explicitly. Live URLs that contain /loop-library/ and the
loop-library-forms Worker name are deployed identifiers and do not change with
this repository layout.
Adding or editing loops
-
The production catalog database is the source of truth for public loops. The current Git tree holds application code and the content-free site shell. Do not commit published loop records, bootstrap data, generated loop pages, catalogs, feeds, sitemaps, or offline catalog fallbacks. Legacy public records remain in pre-migration Git history intentionally; do not rewrite shared history as part of routine catalog work.
-
Publish a reviewed loop from a JSON file outside the repository with:
LOOP_PUBLISH_TOKEN=... \ npm --prefix loop-library/worker run loop:publish -- /path/to/loop.jsonUse
loop-library/worker/examples/loop.jsonas the record template. The command validates the complete record before writing it, and the Worker records every revision. -
Every loop must have a stable slug, unique number, search title and description, contributor attribution, published and modified dates, practical context, verification criteria, category, keywords, and valid related-loop slugs.
-
Do not hand-edit the homepage, detail pages, catalogs, feed, sitemap, or Loopy skill content when publishing a database record. The Worker renders those public surfaces from the same record. New loops use the shared social card unless a reviewed HTTPS
socialImageUrlis supplied. -
Keep bootstrap and backup exports outside the repository with owner-only permissions. The one-time bootstrap command requires an explicit private file path; routine recovery exports use
npm --prefix loop-library/worker run loops:export. Restore an export only into a fresh empty catalog withnpm --prefix loop-library/worker run loops:restore; never overwrite a live catalog. -
Changes to the site shell, Worker, schema, or renderers still go through GitHub. Run the full repository checks before committing those code changes:
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.
- yesterday First seen · 202 lines · 2,320 tokens per session scan A 0a3a463498d1
loopy AGENTS.md is an instructions file published in the GitHub repository Forward-Future/loopy (3,079 stars, last pushed 1mo ago), licensed MIT. It adds 2,320 tokens to every session, about $0.0116 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other instructions, from other repositories
content-factory AGENTS.md
Instructions for mikeshu2001/content-factory, covering content factory - инструкция для агента, главный принцип, что не делать, где искать правила and настройка под проект.
apm python.instructions.md
Python development guidelines.
nextclaw AGENTS.md
Instructions for Peiiii/nextclaw, covering nextclaw ai 常驻内核, 产品愿景, 沟通与推进, 深思与目标模式 and 协作与 git 安全.
slipway AGENTS.md
Instructions for signalridge/slipway, covering slipway agent principles, user owns the process, investigate before clarifying, report, do not certify and maintain the whole surface.
agent-skills AGENTS.md
Instructions for simota/agent-skills, covering agents.md — claude-skills, repository purpose, language policy, repository structure and skill authoring conventions.
loadout shell.instructions.md
Shell Script Engineering Instructions (Bash, CLI wrappers, automation).