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 beefiker/superloopy --skill superloopy-backendgit clone --depth 1 https://github.com/beefiker/superloopyWrote 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/beefiker/superloopy/superloopy-backend)<a href="https://agentmods.dev/skills/beefiker/superloopy/superloopy-backend"><img src="https://agentmods.dev/badge/skills/beefiker/superloopy/superloopy-backend/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/beefiker/superloopy/superloopy-backend"><img src="https://agentmods.dev/badge/skills/beefiker/superloopy/superloopy-backend.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.00116 | $0.02442 |
| Opus 5.5 | $0.00046 | $0.00977 |
| Sonnet 5.5 | $0.00023 | $0.00488 |
| Haiku 4.5 | $0.00012 | $0.00244 |
Grade A, and why
superloopy-backend 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 16d 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 — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SUPERLOOPY BACKEND ENABLED
Open the response with SUPERLOOPY BACKEND ENABLED. If another active Superloopy mode mandates its own first line, print that first and this marker on the next line. Resolve this skill's installed directory, set BACKEND_SKILL_DIR to that absolute path, and announce BACKEND_SKILL_DIR=<path> before loading a reference. Do not assume the repository-relative path is the installed path.
Discover in proportion to the change
Inspect the repository before prescribing commands, code, schema, or infrastructure: its instructions, its recorded conventions and the hooks, linters, formatters, or convention checks that enforce them, language and runtime, data stores and schema authority, test commands, generated artifacts and how they are regenerated, and the project's own definition of done for a change of this kind. Preserve the existing stack and patterns; remain stack-neutral when evidence does not select a technology. Ask only when a missing fact would materially change the implementation or its safety.
Fill the context card only as far as the classified change reaches. A change confined to one unit needs the first six lines; a schema, contract, or runtime-agent change needs all of it. A card filled to the bottom for a two-line fix is cost, not diligence.
User outcome:
Open items the request/ticket states, quoted, each in scope, out (follow-up drafted), or answered:
Language and runtime / existing architecture:
Recorded conventions and their enforcement:
Generated artifacts and their regeneration command:
Project definition of done (one line per item, copied from the project):
Data stores / schema authority:
API consumers / compatibility:
Deployment model / production access / compliance constraints:
Unknowns that affect the decision:
Classify and route
Classify the change as one or more of: API behavior, schema or migration, transaction, background job, cache, event or queue, runtime agent tool, performance, reliability, or security. Load only the modules the classification names:
What ships with it
9 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.
- agents/openai.yaml 322 B
- references/architecture.md 3.7 KB
- references/data-safety.md 5.5 KB
- references/evidence.md 4.3 KB
- references/runtime-agents.md 3.3 KB
- references/sweep.md 3.9 KB
- references/testing-and-operations.md 3.4 KB
- references/upstream-notice.md 8.3 KB
- scripts/write-evidence-report.mjs 12 KB runs code
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.
- 16d ago Changed · +1 lines 482300bb0b54
- 17d ago Changed 0f89446c42a9
- 18d ago Changed ffd1f6df12ab
- 24d ago First seen · 88 lines · 116 tokens per session scan A ba13d3e38613
superloopy-backend is a skill published in the GitHub repository beefiker/superloopy (112 stars, last pushed 2d ago), licensed MIT. It adds 116 tokens to every session and 2,442 once invoked, about $0.0005 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-09-23.
Other skills, from other repositories
data-tables
Manage n8n DataTables (CRUD on tables, columns, rows) via the n8n public REST API. Use when the user wants to create/seed/list/delete data-table resources outside of a workflow — n8nac CLI does not support this. Curl is explicitly allowed for /api/v1/data-tables (carve-out in PreToolUse hook).
data-exchange
A guide for data exchange in 1C. It covers moving changes and messages between databases, including distributed information bases (РИБ), which are connected 1C databases that exchange data.
motherduck-rest-api
Administer MotherDuck service accounts, tokens, Ducklings, and Dive embed sessions through the control-plane REST API.
motherduck-connect
Set up or troubleshoot MotherDuck connections, authentication, client runtimes, and read scaling.
event-store-design
Design and implement event stores for event-sourced systems. Use when building event sourcing infrastructure, choosing event store technologies, or implementing event persistence patterns.
platform-custom-field-generate
Use when users create, generate, or validate Salesforce Custom Field metadata. Trigger on custom fields, field types, Roll-Up Summary, Master-Detail/Lookup relationships, formula fields, picklists, dependent (controlling) picklists, referencing a value set from a field, or scoping picklist values per record type; also…