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/MartyBonacci/specswarmWrote 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/martybonacci/specswarm/tasks)<a href="https://agentmods.dev/commands/martybonacci/specswarm/tasks"><img src="https://agentmods.dev/badge/commands/martybonacci/specswarm/tasks/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/martybonacci/specswarm/tasks"><img src="https://agentmods.dev/badge/commands/martybonacci/specswarm/tasks.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.00018 | $0.02956 |
| Opus 5.5 | $0.00007 | $0.01182 |
| Sonnet 5.5 | $0.00004 | $0.00591 |
| Haiku 4.5 | $0.00002 | $0.00296 |
Grade A, and why
tasks 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 — 243 lines — stays where its author put it; the contents beside it link to each section on GitHub.
User Input
$ARGUMENTS
You MUST consider the user input before proceeding (if not empty).
Canonical Task Line Format (REQUIRED — v7.11.0)
Every task in tasks.md MUST be written as a canonical Markdown checkbox:
- [ ] T001 [P] [US1] <imperative task description> — <relative/file/path>
Rules:
- Start each task line with
- [ ] T###(a literal Markdown checkbox, a space, then the zero-padded task ID). - The checkbox is the source of truth for completion. When a task is finished it becomes
- [X] T###. [P](parallelizable) and[US#](user-story) tags are optional and come after the ID.- This format is language- and stack-agnostic — it carries only the task ID, tags, a description, and an optional file path. It works identically for a Python, Go, Rust, or TypeScript project.
Why this is mandatory: SpecSwarm's tasks-completion-detector PostToolUse hook watches tasks.md for checkbox flips (- [ ] T### → - [X] T###) and auto-queues each completed task for adversarial /ss:verify review. The detector regex is:
^[[:space:]]*-[[:space:]]+\[[xX]\][[:space:]]+T[0-9]+
If tasks are emitted in a heading-only format (e.g. ### T001. …) the detector finds zero matches, the verify-queue stays empty for the whole chunk, and the chunk ships with no per-task spec-mentor verification. Earlier versions emitted heading-form tasks, which silently disabled this layer. The canonical checkbox is now required to keep auto-verification working for every project.
Supplementary detail blocks are allowed but never replace the checkbox. If you also emit ### T001 … headings or a dependency-graph block for human/agent readability, that is fine — but a flat canonical - [ ] T### … checkbox list MUST still be present (either as the primary task lines, or as a dedicated ## Tasks / ## Completion Tracker checklist that mirrors every task ID). The checkbox list is what gets ticked and what the hook reads.
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 · 243 lines · 18 tokens per session scan A 887bf1dc7320
tasks is a command published in the GitHub repository MartyBonacci/specswarm (66 stars, last pushed 2mo ago), licensed MIT. It adds 18 tokens to every session and 2,956 once invoked, about $0.0001 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-08-30.
Other commands, from other repositories
template
Manage issue templates for streamlined issue creation.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
add-note
Add an internal or external note to a ConnectWise PSA ticket.
sync-linear
Sync current work with Linear ticket status.
dispatcher
Use when you want the orchestrator to pick the next repo to work on across your whole portfolio — it enumerates candidate repos below the confinement root, resolves free/busy from each repo's session.lock lease, ranks the FREE ones by backlog priority × staleness × readiness, recommends the single most worthwhile one…
workpm
A project-management workflow for coordinating multiple AI workers through five stages. It includes task assignment, shared activity logs, worker replacement, and final checks.