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 skills/anton-abyzov/specweave/sw-tasknpx skills add anton-abyzov/specweave --skill sw-taskgit clone --depth 1 https://github.com/anton-abyzov/specweaveWrote 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/anton-abyzov/specweave/sw-task)<a href="https://agentmods.dev/skills/anton-abyzov/specweave/sw-task"><img src="https://agentmods.dev/badge/skills/anton-abyzov/specweave/sw-task.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.00046 | $0.01609 |
| Opus 5 | $0.00023 | $0.00805 |
| Sonnet 5 | $0.00009 | $0.00322 |
| Haiku 4.5 | $0.00005 | $0.00161 |
Grade A, and why
sw-task 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 — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.
sw-task — the SpecWeave task ledger
Task state lives in .specweave/increments/<id>/ledger.jsonl: an append-only
JSONL file that any agent, from any vendor, can write. tasks.md holds the task
DEFINITIONS; the ledger holds the STATE. Never edit a ledger line — append.
Two paths, one file format. Run specweave --version:
exit 0 → CLI path (accelerator). Command not found → manual path.
Both produce byte-identical ledger lines.
Formats (copy verbatim)
Task definition in tasks.md — header + one field line:
### T-01 Fold the ledger
- AC: AC-01, AC-02 | Files: src/a.ts, src/a.test.ts | Test: npm test -- a
Files: is the ownership unit: claim the task that owns a file before editing it.
Ledger line — one JSON object per line, keys in this order:
{"t":"T-01","e":"claim","by":"codex@mbp","at":"2026-09-02T10:00:00Z","note":"optional","evidence":"optional"}
ttask id ·eone ofclaimdonereleaseblockskip·byagent id ·atISO-8601 UTC.noteis REQUIRED forskipandblock.evidenceis REQUIRED fordone(test result and/or commit sha).- UTF-8 without BOM, one object per line,
\n-terminated. Blank, malformed and BOM-prefixed lines are skipped and counted, never fatal. - Agent id =
SPECWEAVE_AGENTif set, else<tool>@<short-hostname>(e.g.codex@mbp).
Derived state (how to read the ledger)
Sort events by at (ties: smaller by first), then apply per task:
| Event | Accepted when | Result |
|---|---|---|
claim |
task open, or held by you, or the holder's claim is older than the 2h lease | claimed by <you> |
done |
has evidence, and you hold it / it is open / the claim is stale |
done (terminal) |
release |
you are the holder | open |
block |
open or held by you | blocked + reason |
skip |
has note, not already done/skipped |
skipped (terminal) |
Earliest live claim wins; a claim with no done after 2 hours is stale and
may be taken over. A task with no ledger events is open.
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 · 112 lines · 46 tokens per session scan A 80ec0ef20287
sw-task is a skill published in the GitHub repository anton-abyzov/specweave (159 stars, last pushed today), licensed MIT. It adds 46 tokens to every session and 1,609 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 skills, from other repositories
dream
Batch-execute SHIP-ready wishes overnight — pick wishes, orchestrate workers, review PRs, wake up to results.
clickup
Use when managing ClickUp tasks, sprints, or comments via the cup CLI tool. Triggers: task queries, status updates, sprint tracking, creating subtasks, posting comments, threaded replies, standup summaries, searching tasks, checking overdue items, assigning tasks, listing spaces and lists, opening tasks in browser…
genie-orca-wish
Turn a brainstorm/design into an APPROVED-able wish whose Dispatch plan is the literal input to Orca tasks and Linear issues. High-reasoning pass: pre-decide everything so fast workers can execute without judgment calls.
aigon-next
Suggest the most likely next workflow action based on current context.
aigon-feature-reset
Reset feature - remove worktrees, branches, state, and return lifecycle to backlog.
team
Org-level agent team designer via epic team CLI (cross-project, append-merge). Subcommands: list, show, sync, link, unlink, history. Use when setting up agents, designing teams, or /spec yields 3+ requirements.