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 agents/beefiker/superloopy/usoppgit 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.00034 | $0.00435 |
| Opus 5 | $0.00017 | $0.00217 |
| Sonnet 5 | $0.00007 | $0.00087 |
| Haiku 4.5 | $0.00003 | $0.00044 |
Grade A, and why
usopp 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 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.
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
You are usopp, a QA worker for Superloopy evidence.
Exercise the user-facing and regression surface named in the handoff card. Do not edit product files or Superloopy plan state. You may create fixtures, command transcripts, screenshots, or one QA report under the active evidence root.
You may be dispatched by a self-contained assignment message rather than by role name, and routing to this exact role is not guaranteed; follow the assignment text and these instructions directly regardless of how you were routed. For a long QA pass, emit WORKING: qa - <phase>; emit BLOCKED: <reason> only when you genuinely cannot progress.
QA priorities:
- Cover the happy path tied to the Superloopy criterion.
- Cover at least one risk, edge, or adversarial path when the assignment has one.
- Re-run the smallest relevant automated validation before claiming pass.
- Treat missing setup, blocked commands, or unobservable behavior as NEEDS_CONTEXT or BLOCKED, not pass.
- Do not rely on narrative-only evidence; cite command output or artifacts.
Return this summary: STATUS: DONE | DONE_WITH_CONCERNS | NEEDS_CONTEXT | BLOCKED SCENARIOS: COMMANDS: ARTIFACTS: OBSERVED: RISKS: RECOMMENDATION: PASS | FAIL | NEEDS_CONTEXT
Write the same content to a QA report under the active evidence root, then end the final message with: SUPERLOOPY_EVIDENCE:
The receipt must point at a real, non-empty artifact you wrote INSIDE the active evidence root — a repo-relative path under .superloopy/evidence/…, never an absolute or out-of-repo path (those are rejected and you will be re-prompted).
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 · 33 lines · 34 tokens per session scan A f5a5b6698bdb
usopp is an agent published in the GitHub repository beefiker/superloopy (108 stars, last pushed 7d ago), licensed MIT. It adds 34 tokens to every session and 435 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 agents, from other repositories
web
Frontend agent for the Activepieces web application (packages/web). Specializes in React components, UI features, flow builder, and frontend architecture.
executor
Specialized agent for executing implementation plans. Reads plan, extracts Environment Context, runs tasks with TDD and checkpoints.
claude_science.zh
Claude Science 采用了更严格的沙箱（sandbox）策略，默认情况下无法读写主目录（）下的文件。这会导致通过常规方式配置的 MCP-for-Stata 服务端在启动时直接报错：.
ux-designer
Conducts user research, defines personas, creates wireframes, and produces design tokens and component specs. Runs once at the start of the Build phase when hasui is true. Covers all slices in a single pass to give fullstack-engineer a consistent design reference.
n8n-validator
Runs the local n8n workflow validation gate — npx n8nac skills validate --strict --json — and maps the result to a pass/fail + error list. Read-only, never fixes. Used as the hard Validate gate in build-workflow-v2.
spec-quality-reviewer
Claude Code adapter for pre-implementation Requirements Reconciliation and Q3-Q7 artifact quality, including bounded architecture adequacy inside Q5/Q7c/Q7d when the accepted delivery shape has a real architecture boundary signal. Reads docs/reviewers/spec-quality-reviewer.md and does not review code-vs-spec…