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 AlexShchuka/neuro-matrix --skill agent-fleet-orchestrationgit clone --depth 1 https://github.com/AlexShchuka/neuro-matrixWrote 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/alexshchuka/neuro-matrix/agent-fleet-orchestration)<a href="https://agentmods.dev/skills/alexshchuka/neuro-matrix/agent-fleet-orchestration"><img src="https://agentmods.dev/badge/skills/alexshchuka/neuro-matrix/agent-fleet-orchestration/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/alexshchuka/neuro-matrix/agent-fleet-orchestration"><img src="https://agentmods.dev/badge/skills/alexshchuka/neuro-matrix/agent-fleet-orchestration.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.00065 | $0.01232 |
| Opus 5 | $0.00032 | $0.00616 |
| Sonnet 5 | $0.00013 | $0.00246 |
| Haiku 4.5 | $0.00006 | $0.00123 |
Grade A, and why
agent-fleet-orchestration 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 11d 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 — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent-fleet-orchestration: leading a fleet without drift or false completion
BLUF: the dominant failure modes are contract drift (agents fill unknowns differently, integration breaks), false completion (agent says done, code disagrees), and collisions (two agents touch the same file). This skill eliminates all three structurally.
Stage 0 — decompose into disjoint-scope nodes
- Map the deliverable into nodes where each node owns a non-overlapping set of files or directories. Ownership is a hard partition: no file belongs to two nodes.
- Nodes that share data across a boundary are linked by a contract (interface, schema, wire format), not shared ownership.
- A node that is too large to hold in one agent's context is split further, not given to a stronger model. Size beats capability.
Rule of thumb: if you cannot state a node's output contract in one sentence, split it.
Stage 1 — freeze contracts before any implementation
This is the single most leverage-yielding step. Agents filling nodes against a frozen edge cannot drift relative to each other — the contract is a mechanical stop.
- Author every cross-node interface, function signature, data schema, and wire format as committed files or explicit typed stubs before any implementation agent runs.
- Ambiguous contracts get a
QUESTIONblock (same discipline as paper-to-code Stage 1) — do not resolve ambiguity by picking a default and hoping. - Once frozen, treat the contracts as immutable during the implementation phase; if a contract must change, stop all dependent nodes, revise, and re-fan.
Mirabilis example: the engine (ports & adapters), the Bubble Tea v2 TUI, and the auth-proxy chain each owned a disjoint directory; the port interfaces and the proxy wire protocol were committed as typed Go stubs before any agent wrote implementation code. A contract change mid-flight would have invalidated work in progress — it did not happen.
Stage 2 — parallelize independent nodes, sequence dependent ones
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.
- 11d ago First seen · 77 lines · 65 tokens per session scan A f5d76cc45507
agent-fleet-orchestration is a skill published in the GitHub repository AlexShchuka/neuro-matrix (3 stars, last pushed 2mo ago), licensed MIT. It adds 65 tokens to every session and 1,232 once invoked, about $0.0003 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
last30Days
Resolve "last30Days" to a concrete ISO date range relative to your run time — a rolling 30-day window ending today. Returns inclusive civil dates plus exact UTC instants so you have temporal context without computing dates by hand. Read-only: no writes, no network. Use before a "last 30 days" / trailing-month task…
thisQuarter
Resolve "thisQuarter" to a concrete ISO date range relative to your run time — this quarter so far (quarter start → today). Returns inclusive civil dates plus exact UTC instants so you have temporal context without computing dates by hand. Read-only: no writes, no network. Use before a quarter-to-date task (QTD…
thisWeek
Resolve "thisWeek" to a concrete ISO date range relative to your run time — this week so far (Monday → today). Returns inclusive civil dates plus exact UTC instants so you have temporal context without computing dates by hand. Read-only: no writes, no network. Use before a week-to-date task (this week's activity…
harness
A meta-skill for designing and maintaining a project harness: a coordinated set of specialist agents, skills, and project instructions. It defines their roles, connects them to the project, and updates the setup as the work changes.
md-hive-sync
Munder Difflin hive sync — runs the start-of-task hive protocol steps: reads memory.md, checks inbox/ for new messages, and reminds you to record durable facts in memory.md and write coordination files before ending. Use when asked to "sync with the hive", "check my inbox", "hive status", or "hive sync". Proactively…
md-fetch-summarize
Fetch a URL and return a concise markdown summary of its content. Read-only: no files are written; the summary is returned as output only. Use when asked to "fetch and summarize", "summarize this URL", "what does this page say", or "get the content of ". Proactively suggest when the user pastes a URL and asks what it…