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.
git clone --depth 1 https://github.com/fozzfut/swarm-suiteWrote 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/commands/fozzfut/swarm-suite/swarm-next)<a href="https://agentmods.dev/commands/fozzfut/swarm-suite/swarm-next"><img src="https://agentmods.dev/badge/commands/fozzfut/swarm-suite/swarm-next/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/commands/fozzfut/swarm-suite/swarm-next"><img src="https://agentmods.dev/badge/commands/fozzfut/swarm-suite/swarm-next.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.00015 | $0.00330 |
| Opus 5 | $0.00008 | $0.00165 |
| Sonnet 5 | $0.00003 | $0.00066 |
| Haiku 4.5 | $0.00002 | $0.00033 |
Grade A, and why
swarm-next 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.
What it actually says
You are in Swarm Suite navigator mode. The user typed /swarm-next because they want you to just do the next sensible step rather than ask them to choose.
Do this:
- Call
kb_navigator_state(project_path=<cwd>). - Pick the single highest-priority next action from
suggested_next_steps. Priority order:continue_artifact(anything open and in-flight) wins -- never start something new while a session is mid-flight unless the user explicitly redirects.- If no in-flight artifact: pick the first
stage_continuefor the current stage. - If the stage's main work is done: pick
advance(and confirm with user before destructivekb_advance_pipeline).
- Tell the user what you're about to do and why (one sentence each).
- Confirm with user IF the action is destructive (write to user code, finalise an artifact, advance the pipeline). For all read/scoped tool calls, just do it.
- Execute the tool calls from the picked option's
toolslist, in order, surfacing intermediate results as you go. - After completion, call
kb_navigator_stateagain and tell the user what's next ("done -- next step would be X; want to continue?").
Never ask "which would you like" -- this command means "pick one and run with it." If the user wanted to choose, they'd have used /swarm-status.
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 First seen · 20 lines · 15 tokens per session scan A 6fa6ab5b914c
swarm-next is a command published in the GitHub repository fozzfut/swarm-suite (1 stars, last pushed 4mo ago), licensed MIT. It adds 15 tokens to every session and 330 once invoked, about $0.0001 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 commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.