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 skills add nobrainer-tech/nobrainer-tech-skills --skill nobrainer-dispatchergit clone --depth 1 https://github.com/nobrainer-tech/nobrainer-tech-skillsWrote 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/skills/nobrainer-tech/nobrainer-tech-skills/nobrainer-dispatcher)<a href="https://agentmods.dev/skills/nobrainer-tech/nobrainer-tech-skills/nobrainer-dispatcher"><img src="https://agentmods.dev/badge/skills/nobrainer-tech/nobrainer-tech-skills/nobrainer-dispatcher/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/skills/nobrainer-tech/nobrainer-tech-skills/nobrainer-dispatcher"><img src="https://agentmods.dev/badge/skills/nobrainer-tech/nobrainer-tech-skills/nobrainer-dispatcher.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00088 | $0.02426 |
| Opus 5 | $0.00044 | $0.01213 |
| Sonnet 5 | $0.00018 | $0.00485 |
| Haiku 4.5 | $0.00009 | $0.00243 |
Grade A, and why
nobrainer-dispatcher 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 8d 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 — 230 lines — stays where its author put it; the contents beside it link to each section on GitHub.
NoBrainer Dispatcher
Turn an approved detailed plan into a controlled sequence of work batches. Own readiness, ordering, backpressure and scheduler state; never own requirements, implementation, session identity or final acceptance evidence.
Keep the boundaries explicit:
nobrainer-ultraowns intent, the canonical plan and lifecycle;nobrainer-teamowns the minimum roles and capability sources;- Dispatcher owns which already-defined work unit may run now;
nobrainer-sessionsowns exact session identity, transport, lease and receive-audit;- the assigned method owns the work product;
nobrainer-reviewowns the independent close gate when required.
A single coherent work unit stays in MAIN and marks Dispatcher NOT_NEEDED.
Parallelism is an optimization earned by independent work, not the default.
When the owner explicitly invokes Dispatcher only to inspect such a map,
Dispatcher owns that scheduler inspection and returns NOT_NEEDED; MAIN remains
the owner of the work unit and its product. Keep control ownership distinct from
work ownership in every report.
Preconditions
Dispatch only from a visible canonical ledger whose executable rows contain:
TASK_ID | OUTCOME | METHOD | MODEL_POLICY | OWNER_OR_ROLE | DEPENDENCIES | WRITE_SCOPE |
ACCEPTANCE_AND_EVIDENCE | PARALLEL_GROUP | OWNER_GATE | STATUS
Also require the frozen plan/spec ref, current checkout and state fingerprint,
retry and attention budgets, stop conditions, integration owner and rollback.
If requirements, task boundaries, dependencies, acceptance or authority remain
undefined, return to nobrainer-ultra; Dispatcher must not repair a vague plan
by improvising worker prompts.
Before assigning any worker, require a completed nobrainer-team capability
and role stage. Use one canonical cross-skill transition:
Team -> Dispatcher SCHEDULE -> Sessions setup/delegate -> Dispatcher DISPATCH
Sessions alone owns identity preflight and prompt transport. Dispatcher selects
the batch before that call and records READY -> SENT only from Sessions'
successful transport readback. A role name or conversation title is not a
transport address.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 8d ago Changed · +11 lines · -1 tokens per session 0e48aecc273e
- 12d ago First seen · 219 lines · 89 tokens per session scan A 5be28a908cb5
nobrainer-dispatcher is a skill published in the GitHub repository nobrainer-tech/nobrainer-tech-skills (5 stars, last pushed 7d ago), licensed MIT. It adds 88 tokens to every session and 2,426 once invoked, about $0.0004 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 skills, from other repositories
project-init
Interview-based project setup — generates CLAUDE.md, ROADMAP, .gitignore, .env.example from scratch. Use when: user says '/project-init', 'new project', 'project creation', 'project setup', 'project setup', 'new project', 'create project'. NOT for AI agent/harness configuration (use setup for that). Conversational…
project-overview
Use when the user wants a deterministic cross-project status map generated from registered projects' session handoffs. Triggers: '/project-overview', 'project map', 'overall status'. Reads /.claude/projects-registry.md (opt-in list), parses each project's memory/session-handoff-LATEST.md state-snapshot v1 block…
session-start
Load handoff on session start, review lessons, output readiness signal. Triggers: '/session-start', 'start session'. Skip if: first session (no handoff), user requests 'start fresh', or standalone question unrelated to project context.
multi-agent-loop
Turn the current repository into a supervised multi-agent coding loop — spawn parallel AI coding agents in isolated git worktrees with file ownership, a shared radar, and human approval gates, then run the loop (status, standup, approvals) from one place.
parallel-feature-development
Coordinate parallel feature development with file ownership strategies, conflict avoidance rules, and integration patterns for multi-agent implementation. Use this skill when decomposing a large feature into independent work streams, when two or more agents need to implement different layers of the same system…
track-management
Use this skill when creating, managing, or working with Conductor tracks - the logical work units for features, bugs, and refactors. Applies to spec.md, plan.md, and track lifecycle operations.