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/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/skills/anton-abyzov/specweave/increment"><img src="https://agentmods.dev/badge/skills/anton-abyzov/specweave/increment.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 55 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.01419 |
| Opus 5.5 | $0.00018 | $0.00568 |
| Sonnet 5.5 | $0.00009 | $0.00284 |
| Haiku 4.5 | $0.00005 | $0.00142 |
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 — 115 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/, with one file you write:
spec.md. ledger.jsonl beside it holds task state and is only appended to;
metadata.json is machine state you never need to read. One increment is one branch
and one PR.
Before writing
- A small self-contained fix needs no increment. Just do it.
- An open increment already owns the files this touches (
specweave task list)? Add ACs and tasks to its spec.md instead of opening another. - Read the code the change touches before writing Approach. If
GLOSSARY.mdexists, write the spec in its terms. - Unsure what to build at all, or the user says "grill me": run sw-grill-me first
(
specweave skills enable grill-meinstalls it).
Decide
Intent first: settle what the user wants and how a machine will check it before
writing ACs. planning.deepInterview sets the depth: critical (default) as below,
deep runs sw-grill-me, off states defaults and asks nothing.
- Think first. Read the code and config; settle every fact yourself.
- Triage each open decision: fact (look it up, never ask), my call (reversible or low impact: pick a default), theirs (hard to reverse, costly, taste).
- Ask only "theirs", at most 5, highest impact first. Each gets one clause on why it matters and 2 to 4 options, your recommendation first; "yes" accepts it. Use your tool's structured question tool when it has one. A clear request asks nothing.
- Record in
## Decisions: Asked, Defaulted (list every default: one the user never saw is one they could not reject) and Open. Keep a line only when a later change could contradict it: hard to reverse, surprising without context, or a real trade-off. Apply each answer to Scope, ACs and Approach.
Create it
specweave create-increment "Add rate limiting" prints the new folder with a scaffolded
spec.md; replace every [bracket]. Add --supersedes 0031 when this replaces an older
increment (that one is abandoned for you), --planned for backlog work.
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 Changed · +4 lines 53bbae44e306
- 5d ago Changed · +9 lines 786955c472a4
- 6d ago Changed · +17 lines d243ae314088
- 11d ago Changed · +5 lines e6a795137142
- 27d ago Changed · -26 lines · +2 tokens per session 30cb58697734
- 1mo ago Changed · +2 lines 467d36783802
- 1mo ago First seen · 104 lines · 44 tokens per session scan A 6375f9511eaf
increment is a skill published in the GitHub repository anton-abyzov/specweave (167 stars, last pushed today), licensed MIT. It adds 46 tokens to every session and 1,419 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
follow-up-after-call
Use after a completed customer, prospect, partner, or important internal sales call, discovery session, demo, or conversation, including when the user supplies or uploads a transcript, notes, recording summary, or other grounded evidence. Advise on, assess, qualify, recap, and produce seller-ready follow-up actions…
persona-event-coordinator
Plan and manage events — scheduling, invitations, and logistics.
persona-project-manager
Coordinate projects — track tasks, schedule meetings, and share docs.
persona-team-lead
Lead a team — run standups, coordinate tasks, and communicate.
ulw-execute
Executes a written ulw-plan work plan with Boulder state, evidence ledger, worktree discipline, and parallel subagents. Use when the user says ulw-execute or asks to run a .omo/plans plan.
recipe-plan-weekly-schedule
Review your Google Calendar week, identify gaps, and add events to fill them.