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.
git clone --depth 1 https://github.com/kok-o/koko-contextos-agentsWrote 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/rules/kok-o/koko-contextos-agents/subagent-orchestrator)<a href="https://agentmods.dev/rules/kok-o/koko-contextos-agents/subagent-orchestrator"><img src="https://agentmods.dev/badge/rules/kok-o/koko-contextos-agents/subagent-orchestrator/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/rules/kok-o/koko-contextos-agents/subagent-orchestrator"><img src="https://agentmods.dev/badge/rules/kok-o/koko-contextos-agents/subagent-orchestrator.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.00027 | $0.00853 |
| Opus 5 | $0.00014 | $0.00426 |
| Sonnet 5 | $0.00005 | $0.00171 |
| Haiku 4.5 | $0.00003 | $0.00085 |
Grade A, and why
subagent-orchestrator 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 4d 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 — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: subagent-orchestrator
subagent-orchestrator
Overview
Multi-agent coordination protocol inspired by obra/superpowers. Enables a primary orchestrating agent to decompose complex workflows into isolated, parallel sub-tasks, delegate them with precise context boundaries, monitor execution, and synthesize outputs with zero merge conflicts.
When to Use
Activate whenever:
- A task can be parallelized across distinct modules, services, or test suites.
- Long-running exploratory research or multi-file refactoring exceeds single-context budget.
- Running autonomous subagent workers for specialized roles (e.g. specialized QA tester, Security auditor, Docs generator).
Rules & Patterns
1. The Blast Radius Boundary Rule
Before delegating any subagent task:
- Zero File Overlap: Each subagent MUST have a mutually exclusive list of target files. Two subagents must never be instructed to edit the same file concurrently.
- Explicit Inputs & Outputs: Provide only the minimal schema, contract, or mock that the subagent needs. Do not dump the entire workspace into subagent prompts.
2. The 4-Step Delegation Lifecycle
[ Orchestrator ]
│
├─▶ 1. DECOMPOSE: Break into orthogonal tasks with non-overlapping file sets
│
├─▶ 2. DISPATCH: Launch subagent with precise goal, constraints, and finish criteria
│
├─▶ 3. AWAIT & VERIFY: Validate subagent output against its individual quality gate
│
└─▶ 4. SYNTHESIZE: Merge subagent results into the main branch and run global regression suite
3. Context Hand-off Specification
Every subagent dispatch prompt must contain:
- Target Objective: Single, verifiable deliverable.
- Read-Only Context: Files to consult as reference without modifying.
- Write Scope: Exact file paths the subagent is permitted to create or modify.
- Completion Signal: Explicit instruction to report
DONEwith test evidence orBLOCKEDwith reason.
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.
- 4d ago First seen · 103 lines · 27 tokens per session scan A f6e471a0ce50
subagent-orchestrator is a cursor rule published in the GitHub repository kok-o/koko-contextos-agents (2 stars, last pushed 5d ago), licensed MIT. It adds 27 tokens to every session and 853 once invoked, about $0.0001 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-09-05.
Other cursor rules, from other repositories
deepen-architecture
Find deepening opportunities in a codebase, informed by the domain language in specs/tech-architecture/tech-stack.md and the decisions in specs/adr/. Use when the user wants to improve architecture, find refactoring opportunities, consolidate tightly-coupled modules, or make a codebase more testable and AI-navigable.
craft-skill
Create new bigpowers skills with proper structure, progressive disclosure, and bundled resources. Use when user wants to create, write, or build a new skill for the bigpowers lifecycle.
grill-me
Interactive assumption-surfacing Q&A that stress-tests a plan through relentless questioning until every decision is resolved. Use when user wants to challenge a plan, validate decisions from conversation/context, or mentions "grill me". For doc-grounded variant, use grill-with-docs.
run-planning
DISCOVER-PHASE ADVANCER — Drive the discover-phase checklist (specs/planning-status.yaml) through survey-context → scope-work → research-first → elaborate-spec → plan-release → slice-tasks. NOT a duplicate of plan-work or the planning spine; it orchestrates the pre-coding discover phase only.
slice-tasks
PLANNING SPINE STEP 2 of 3 — Slice the work: break a scoped PRD into vertical-slice stories in specs/epics/. Use after scope-work (step 1), before plan-work (step 3). Not a substitute for scope-work or plan-work.
terse-mode
Fallback ultra-compressed communication mode. Cuts token usage 75% by dropping filler, articles, and pleasantries while keeping full technical accuracy. Use ONLY when context is critically long and compressing output is necessary to continue. Not a strategy — token discipline comes from code shape (small functions…