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 rules/alphabitcore/nexus-gateway/sub-agent-dispatchgit clone --depth 1 https://github.com/AlphaBitCore/nexus-gatewayWhat 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.00342 | $0.00342 |
| Opus 5 | $0.00171 | $0.00171 |
| Sonnet 5 | $0.00068 | $0.00068 |
| Haiku 4.5 | $0.00034 | $0.00034 |
Grade A, and why
sub-agent-dispatch 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
Sub-agent dispatch discipline (binding)
Sub-agents have zero session context. Terse prompts produce shallow work. Use them only where the gain is real and the prompt is complete.
OK to delegate
- (a) Mechanical multi-file work that doesn't need main-context reasoning — test stub renames, doc cross-rewrites, codemod-style edits.
- (b) Parallel-safe independent research lookups —
Exploreagent for code search, "find me where X is referenced." - (c) Bounded scope where the agent's report-back is enough — small audits, well-defined formatting passes.
DO NOT delegate
- Understanding a new problem — the main agent must keep the model.
- Decisions that change scope or contract — those need user-in-the-loop, not a sub-agent.
git commit/git push/ force-pushes / destructive ops on shared history — never via sub-agent.
Required prompt shape
Every dispatched prompt MUST include:
- (i) Goal + non-goals in the first 3 lines.
- (ii) Which worktree the agent is operating in if non-default.
- (iii) Demand a 2-round self-audit before report-back.
- (iv) Ask for a per-file list of touched paths + verification command outputs in the response.
Skipping this rule requires explicit user approval in chat.
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 · 32 lines · 342 tokens per session scan A 82319d638771
sub-agent-dispatch is a cursor rule published in the GitHub repository AlphaBitCore/nexus-gateway (22 stars, last pushed 7d ago), licensed Apache-2.0. It adds 342 tokens to every session, about $0.0017 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 cursor rules, from other repositories
plugin-development
Plugin Development Standards - Applies to all new wasm and golang-filter plugins.
reachai-project
ReachAI project rules for AI coding agents.
10-deterministic-audit
Enforce deterministic audit behavior — no invented controls, cite authoritative sources, emit traceable artifacts.
recipe_author
How to author a recipe in ks-cookbook.
30-framework-routing
Route tasks to HIPAA, HITECH, PCI-DSS, SOC 2, ISO 27001, NIST CSF, NIST AI RMF, FERPA, COPPA, CCPA, US state privacy, GDPR, FedRAMP, SOX, CMMC, and GLBA skills based on user intent and presets.
00-compliance-agent-core
Core compliance agent mission, PHI redaction gate, and audit lifecycle for HIPAA, PCI-DSS, and SOC 2.