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 anton-abyzov/specweave --skill sw-incrementgit 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-increment)<a href="https://agentmods.dev/skills/anton-abyzov/specweave/sw-increment"><img src="https://agentmods.dev/badge/skills/anton-abyzov/specweave/sw-increment.svg" alt="Measured on agentmods" 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.00049 | $0.01041 |
| Opus 5 | $0.00024 | $0.00521 |
| Sonnet 5 | $0.00010 | $0.00208 |
| Haiku 4.5 | $0.00005 | $0.00104 |
Grade A, and why
sw-increment 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 4d 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 — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
sw-increment — plan the unit of work
An increment is one folder, .specweave/increments/NNNN-slug/, and it is the
tracker: spec + tasks + ledger + evidence live together and travel in git.
Write the spec, get it approved, then implement (sw-do). No code before the
ACs exist.
Run specweave --version: exit 0 → CLI path. Not found → manual path.
1. Understand before writing
Ask only what you cannot infer from the repo — typically: the problem behind the request, what is explicitly out of scope, and how you will know it works. Scope clear from the request? Skip the interview and write the spec.
2. Create the folder
CLI:
specweave create-increment --auto-id --name "<slug>" --title "<Title>" \
--description "<one line>" --project "<project id from .specweave/config.json>" \
[--type feature|bug|hotfix|refactor|experiment]
Manual: next id = highest existing number + 1, zero-padded to 4
(ls .specweave/increments), folder NNNN-kebab-slug, then write
metadata.json, spec.md, tasks.md, and an empty ledger.jsonl:
{"id":"0042-ledger-fold","status":"active","type":"feature","created":"2026-09-02T10:00:00Z","lastActivity":"2026-09-02T10:00:00Z"}
Write every file as UTF-8 without a BOM (PowerShell:
[IO.File]::WriteAllText($p, $body, [Text.UTF8Encoding]::new($false)), never >)
— a BOM breaks the parsers that read these files on the next machine.
Status is one of planning active paused ready_for_review completed
abandoned, and only lifecycle commands change it. Replacing an older
increment? Add "supersedes":"0031-old-slug" here and close that one as
abandoned with the reason superseded by 0042-ledger-fold.
3. spec.md — one evolving document
# 0042 Ledger fold
## Problem
What is wrong today and for whom. The intent, not the solution.
## Scope
In: … · Out: … (say what you are deliberately not doing)
## Acceptance criteria
- [ ] AC-01 Two agents claiming the same task never both get it
- [ ] AC-02 A malformed ledger line is skipped and counted, never fatal
## Approach
Files that change and in what order · risks · decisions taken (link ADRs) ·
alternatives rejected and why.
## Open questions
- …
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.
- 4d ago First seen · 105 lines · 49 tokens per session scan A 4581fb9f0a72
sw-increment is a skill published in the GitHub repository anton-abyzov/specweave (160 stars, last pushed yesterday), licensed MIT. It adds 49 tokens to every session and 1,041 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
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.
linear-graphql-skill
Operate Linear workspace issues, projects, and teams through Linear GraphQL API using UXC. Use when tasks require querying or creating issues, managing projects, or interacting with Linear workflow. Supports both Personal API Key and OAuth authentication.
dos-dispatch
Plan and ship the next batch on one lane: run dos-next-up, acquire a lease with dos arbitrate, gate empty work, dispatch the packet, and archive the run. Use when a single lane should move end to end with collision safety.
dos-next-up
Snapshot the repo's phased-plan portfolio into a dispatch packet: audit candidates with dos verify, render who-does-what, and emit a dos gate verdict. Use when you need the current next-work view before dispatching agents.
aigon-next
Suggest the most likely next workflow action based on current context.