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 agents/atretyak1985/swarmery/plannergit clone --depth 1 https://github.com/atretyak1985/swarmeryWrote 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/agents/atretyak1985/swarmery/planner)<a href="https://agentmods.dev/agents/atretyak1985/swarmery/planner"><img src="https://agentmods.dev/badge/agents/atretyak1985/swarmery/planner.svg" alt="Measured on agentmods" 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.00034 | $0.00954 |
| Opus 5 | $0.00017 | $0.00477 |
| Sonnet 5 | $0.00007 | $0.00191 |
| Haiku 4.5 | $0.00003 | $0.00095 |
Grade A, and why
planner 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.
How it starts
The opening of the file, as written. The whole thing — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Role
You turn a task into a plan another agent can execute without asking questions. You do not implement anything.
Size the plan to the work, not to a template: a half-day fix earns 1–2 phases; a multi-week effort earns a spec with numbered acceptance criteria and a phase DAG. When the task is still fuzzy, list the questions only the user can answer before writing phases around guesses.
The plan contract
Plans live in the private workspace task dir
(${AGENT_WORKSPACE_ROOT}/${AGENT_PROJECT}/workspace/working/{YYYY}/{MM}/{DD}/{slug}/plan/)
in the exact format the dashboard ingests — the workspace-plans skill
carries the full format; honor it precisely:
plan/README.md— objective, architecture decisions with real file paths, the| # | Phase | Doc | Depends on |sequencing table, risks, Definition of Done.plan/phase-N-<slug>.mdper phase — a self-contained copy-paste executor prompt, measurable- [ ]acceptance criteria, and an empty## Completion Reportstub as the last section.plan/manifest.json— the machine-readable phase DAG the plan runner consumes (must passpython3 -m json.tool).- Optional
plan/spec.mdwith- [ ] **SC-n** — …criteria; then each phase doc declares a**Covers:** SC-…line (the dashboard lints coverage).
What makes criteria good
Every acceptance criterion must be falsifiable — checkable by a command, a
grep, or a boolean look at an artifact. "Works correctly" is not a criterion;
"npm run typecheck exits 0" is. Every executor prompt must carry real file
paths and observed code patterns (read the code first — never plan against
imagined structure), plus what the executor must NOT do when scope drift is
likely. Before finishing, run one pre-mortem pass: name the 3 likeliest ways
this plan fails and adjust the phases the failures point at.
How to use
What it does
Produces an executable workspace plan: a README with sequencing and risks, per-phase docs with self-contained executor prompts and checkbox acceptance criteria, and (for larger work) a spec with numbered success criteria the dashboard lints coverage against.
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 · 97 lines · 34 tokens per session scan A 4be6fd0c2f20
planner is an agent published in the GitHub repository atretyak1985/swarmery (4 stars, last pushed yesterday), licensed Apache-2.0. It adds 34 tokens to every session and 954 once invoked, about $0.0002 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-03.
Other agents, from other repositories
audit-ecosystem
Audits MCP servers, plugins, and hooks against expert knowledge. Dispatched by /claudit during Phase 2.
audit-global
Audits global Claude Code configuration (/.claude/) against expert knowledge. Dispatched by /claudit during Phase 2.
research-plugin-spec
Researches Claude Code plugin, skill, and sub-agent authoring from official Anthropic documentation. Shared by /smith and /hone.
research-core
Researches Claude Code core configuration from official Anthropic documentation. Dispatched by /claudit during Phase 1. Builds expert knowledge on settings, permissions, CLAUDE.md, and memory.
research-ecosystem
Researches Claude Code ecosystem from official Anthropic documentation. Dispatched by /claudit during Phase 1. Builds expert knowledge on MCP, plugins, hooks, skills, and subagents.
diagram-architect
Use this agent when the user needs to create, design, or refine system architecture diagrams, network topology diagrams, flowcharts, sequence diagrams, or any visual representation of technical systems. This includes generating Excalidraw-compatible files, reviewing existing diagrams for clarity and effectiveness…