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 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/increment)<a href="https://agentmods.dev/skills/anton-abyzov/specweave/increment"><img src="https://agentmods.dev/badge/skills/anton-abyzov/specweave/increment.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.00044 | $0.01409 |
| Opus 5 | $0.00022 | $0.00705 |
| Sonnet 5 | $0.00009 | $0.00282 |
| Haiku 4.5 | $0.00004 | $0.00141 |
Grade A, and why
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 3d 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 — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plan an Increment
An increment is one folder — .specweave/increments/NNNN-slug/ — holding
spec.md (intent + ACs + approach), tasks.md (task definitions),
ledger.jsonl (state, written by the CLI) and metadata.json. It is the unit of
work and the tracker; every commit for it carries its id in the subject.
Plan mode first (blocking)
Planning produces a document the user approves before any code is written. If your
tool has a plan mode, enter it now (Claude Code: EnterPlanMode) and wait for
confirmation. Do not create files, do not implement, until the plan is approved.
Steps
- Understand the request. Restate it in one sentence: what changes, for whom, why now.
- Scope clear enough to write ACs? Go to 2.
- Not clear (vague goal, unknown users, competing options, unclear done-condition)? Interview first — ask only the questions whose answers change the spec, in one batch: the problem behind the request, who hits it, what "done" looks like, what is explicitly out of scope, constraints (stack, deadline, data), and the riskiest unknown. Trivial fix → 0 questions. Do not interview to fill a quota.
- Look before writing. Read
.specweave/config.json(testing commands, sync,workspace.repos), skim existing increments for overlap (specweave status), and read the code the change will touch. An Approach written without reading the files is a guess. - Create the folder — the CLI owns id allocation (atomic, retried):
Superseding an older increment: passspecweave create-increment --auto-id --name "<kebab-slug>" --title "<Title>" \ --description "<one line>" --project "<project id from config>" \ [--type feature|bug|hotfix|refactor] [--supersedes <old-id>]--supersedes <old-id>. That one command abandons the old increment withcloseReason: "superseded by <new-id>"and recordssupersedeson the new one — do not split it into two steps. Name the old id in the new spec's Problem section. No CLI: create the folder by hand, put"supersedes": "<old-id>"in the newmetadata.jsonand set the old one to"status": "abandoned"with the samecloseReason. - Write
spec.md— one evolving document, these sections:
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.
- 3d ago First seen · 104 lines · 44 tokens per session scan A 6375f9511eaf
increment is a skill published in the GitHub repository anton-abyzov/specweave (159 stars, last pushed today), licensed MIT. It adds 44 tokens to every session and 1,409 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.
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.
aigon-feature-unprioritise
Move a backlog feature back to inbox (slug filename).