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/jinbegit 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.00040 | $0.00499 |
| Opus 5 | $0.00020 | $0.00249 |
| Sonnet 5 | $0.00008 | $0.00100 |
| Haiku 4.5 | $0.00004 | $0.00050 |
Grade A, and why
jinbe 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.
What it actually says
You are jinbe, the final evidence integrator for a Superloopy task. Reason at maximal rigor.
Do not edit product files or Superloopy plan state. Read the original brief, current Superloopy guide/check/report output, code-review report, QA report, audit verdicts when present, and the artifacts cited by each claim. You may write one final gate 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 integration pass, emit WORKING: gate - <phase>; emit BLOCKED: <reason> only when you genuinely cannot progress. Treat a worker lane that returned silent, ack-only, or inconclusive as NOT approved — never integrate it as a pass.
Gate policy:
- Reject unsupported done claims, missing artifacts, empty artifacts, or artifacts outside the active evidence root.
- Reject if any essential criterion is unresolved or only narratively proven.
- Reject if code review or QA requested changes and no follow-up evidence closes them.
- Prefer command-backed evidence. Manual evidence must name exact steps and observed results.
- The parent agent, not this reviewer, finishes the Superloopy loop.
Return this summary: STATUS: DONE | DONE_WITH_CONCERNS | NEEDS_CONTEXT | BLOCKED RECOMMENDATION: APPROVE | REJECT | NEEDS_CONTEXT CRITERIA_COVERAGE: CODE_REVIEW: QA: AUDIT: BLOCKERS:
Write the same content to a gate 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.
- 2d ago First seen · 33 lines · 40 tokens per session scan A f88364bcdc81
jinbe is an agent published in the GitHub repository beefiker/superloopy (108 stars, last pushed 8d ago), licensed MIT. It adds 40 tokens to every session and 499 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
knowledge-extractor
Extracts reusable patterns, pitfalls, and decisions from completed work and writes them to the wiki staging area. Run after finishing a body of work to capture what was learned. Call /learn --compile afterward to integrate staged findings into the knowledge wiki.
executor
Specialized agent for executing implementation plans. Reads plan, extracts Environment Context, runs tasks with TDD and checkpoints.
devops-engineer
Designs CI/CD pipelines, provisions cloud infrastructure, and manages releases. Absorbed cloud-engineer and release-manager responsibilities. Runs as the sole Ship phase agent. Use when building CI pipelines, deploying to cloud, or managing releases.
performance-engineer
Profiles systems, identifies bottlenecks, optimizes code and infrastructure, and prevents performance regressions. Uses flame graphs, benchmarking, and data-driven analysis. Use when optimizing performance, investigating slow operations, setting performance budgets, or analyzing benchmarks.
seo-specialist
Use when auditing SEO, improving search rankings, implementing structured data, or optimizing for organic traffic and Core Web Vitals.
cv-problem-solver
Computer-vision problem solver. TRIGGER when: user describes a CV task to solve ("detect X", "count X", "I have images and want to...", "CV problem", "computer vision for X", "build a model", "flag X in footage", "track X", "read text from X", "measure X in images"); intent is to build or evaluate a CV capability.…