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/mjunaidca/robolearn/super-orchestragit clone --depth 1 https://github.com/mjunaidca/robolearnWhat 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.00119 | $0.05631 |
| Opus 5 | $0.00060 | $0.02815 |
| Sonnet 5 | $0.00024 | $0.01126 |
| Haiku 4.5 | $0.00012 | $0.00563 |
Grade A, and why
super-orchestra 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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 · 482 lines · 119 tokens per session scan A 4ac428047981
super-orchestra is an agent published in the GitHub repository mjunaidca/robolearn (9 stars, last pushed 7mo ago), with no licence file. It adds 119 tokens to every session and 5,631 once invoked, about $0.0006 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-31.
Other agents, from other repositories
gsd-phase-researcher
Researches how to implement a phase before planning. Produces RESEARCH.md consumed by gsd-planner. Spawned by /gsd:plan-phase orchestrator.
pdca-iterator
Evaluator-Optimizer pattern agent for automatic iteration cycles. Orchestrates the Generator-Evaluator loop in the PDCA Check-Act phase until quality criteria are met. Use proactively when gap analysis reports Match Rate below 90%, /pdca-iterate is executed, or user requests automatic fixing or iterative improvement.…
pm-lead
PM Team Lead agent that orchestrates the PM Agent Team workflow. Coordinates pm-discovery, pm-strategy, pm-research, and pm-prd agents to produce a comprehensive PRD before PDCA Plan phase. Triggers: pm team, product discovery, PM analysis.
report-generator
Agent that automatically generates PDCA cycle completion reports. Consolidates plan, design, implementation, and analysis results into learnable reports. Use proactively when user completes PDCA cycle, finishes feature implementation, or requests summary/status report of development progress. Triggers: PDCA report…
gap-detector
Agent that detects gaps between design documents and actual implementation. Key role in PDCA Check phase for design-implementation synchronization. Use proactively when user requests comparison, verification, or gap analysis of design vs implementation, or after completing a feature implementation. Triggers: gap…
spec-tdd-impl-agent
Execute implementation tasks using Test-Driven Development methodology.