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 pjt222/agent-almanac --skill coordinate-swarmgit clone --depth 1 https://github.com/pjt222/agent-almanacWrote 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/pjt222/agent-almanac/coordinate-swarm)<a href="https://agentmods.dev/skills/pjt222/agent-almanac/coordinate-swarm"><img src="https://agentmods.dev/badge/skills/pjt222/agent-almanac/coordinate-swarm/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/pjt222/agent-almanac/coordinate-swarm"><img src="https://agentmods.dev/badge/skills/pjt222/agent-almanac/coordinate-swarm.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.00091 | $0.02649 |
| Opus 5.5 | $0.00036 | $0.01060 |
| Sonnet 5.5 | $0.00018 | $0.00530 |
| Haiku 4.5 | $0.00009 | $0.00265 |
Grade A, and why
coordinate-swarm 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 1mo 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 — 200 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Coordinate Swarm
Establish coordination across distributed agents using stigmergy (indirect communication through environment modification), local interaction rules, and quorum sensing — enabling coherent collective behavior without a central controller.
When to Use
- Designing distributed systems where no single node should be a coordination bottleneck
- Organizing teams or workflows that must self-coordinate without constant management oversight
- Building event-driven architectures where components communicate through shared state rather than direct messaging
- Scaling a process that works well with 3 agents but breaks down at 30
- Bootstrapping coordination patterns for a new swarm-style domain (see
forage-resources,build-consensus) - Replacing fragile centralized orchestration with resilient emergent coordination
Inputs
- Required: Description of the agents (workers, services, team members) that need coordination
- Required: The collective goal or desired emergent behavior
- Optional: Current coordination mechanism and its failure modes
- Optional: Number of agents (affects pattern selection — small swarms vs. large colonies)
- Optional: Latency tolerance (real-time vs. eventual coordination)
- Optional: Environmental constraints (shared state availability, communication bandwidth)
Procedure
Step 1: Identify the Coordination Problem Class
Classify the coordination challenge to select appropriate patterns.
- Map the current state: who are the agents, what do they do individually, where does coordination break down?
- Classify the problem:
- Foraging — agents search for and exploit distributed resources (see
forage-resources) - Consensus — agents must agree on a collective decision (see
build-consensus) - Construction — agents build or maintain a shared structure incrementally
- Defense — agents detect and respond to threats collectively (see
defend-colony) - Division of labor — agents must self-organize into specialized roles
- Foraging — agents search for and exploit distributed resources (see
- Identify the failure mode of current coordination:
- Single point of failure (centralized controller)
- Communication bottleneck (too many direct messages)
- Coherence loss (agents drift apart without feedback)
- Rigidity (cannot adapt to changing conditions)
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.
- 1mo ago First seen · 200 lines · 91 tokens per session scan A 961860b66621
coordinate-swarm is a skill published in the GitHub repository pjt222/agent-almanac (42 stars, last pushed 5d ago), licensed MIT. It adds 91 tokens to every session and 2,649 once invoked, about $0.0004 per session on Opus 5.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-03.
Other skills, from other repositories
audit-pr
Audit a whole PR against the delivery contract and return MERGE-READY or evidenced blockers with the full URL. Consumes the current review-change REVIEW-PASS receipt instead of re-running review axes; posts a SHA-bound ready comment; never edits or merges. Triggers: "audit-pr", "is this PR ready", "merge gate".
execute-phase
Step executor for units whose triage (unit-lane) decided which steps the unit needs. Implements one triaged step (or all remaining steps), with frozen acceptance, step-local gates, commits, red-gate repair, and diff-size guard. BREAKING: replaced PLAN.md/TASKS.md/progress.md/ACCEPTANCE.md with the unit doc's Tasks…
fold-findings
Repair persisted fix-now findings in compatible atomic batches: root-cause fixes, green gate, commit/push, and per-row folded: yes updates. Never reclassify or substitute backlog notes. Triggers: "fold-findings", "fix the review findings", "repair audit blockers".
init-workspace
Adapt the workflow scaffold to a new repository or add only missing substrate blocks to an existing install. Every install, hook, and overwrite needs explicit consent. Triggers: "init-workspace", "set up agentic workflow", "upgrade workflow scaffold".
product-audit
Audit the whole product across code, quality, process, docs, roadmap, and tooling; it owns the repo-wide bug hunt, security research, and broken-version investigation (scoped and budgeted per dimension, as distinct from review-change's change-scoped review). Persist one severity-ranked, F-numbered report with…
review-change
Review a change with only applicable internal axes, classify every finding, persist fix-now work, and return one evidence-backed decision. Findings only; --adversarial N uses isolated reviewers; --synthesize fuses supplied reviewer tables. Triggers: "review-change", "review this change", "adversarial review".