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 donegit 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/done)<a href="https://agentmods.dev/skills/anton-abyzov/specweave/done"><img src="https://agentmods.dev/badge/skills/anton-abyzov/specweave/done/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/done"><img src="https://agentmods.dev/badge/skills/anton-abyzov/specweave/done.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to high
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 →
- high Tool Misuse · line 35 Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
- medium Tool Misuse · line 35 Tool defaults are unsafe or overly permissive (e.g. disabled TLS verification, no authentication, world-writable permissions). Unsafe defaults widen the attack surface.Fix: Override unsafe defaults with secure settings (verify=True, auth required, restrictive permissions). Review and harden all tool configurations.
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.00045 | $0.00695 |
| Opus 5.5 | $0.00018 | $0.00278 |
| Sonnet 5.5 | $0.00009 | $0.00139 |
| Haiku 4.5 | $0.00005 | $0.00069 |
Grade A, and why
done 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 6d 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 — 52 lines — stays where its author put it; the contents beside it link to each section on GitHub.
sw-done: close an increment
Closing is verify, review, complete. The one hard gate is a passing
reports/verify.json; everything else is evidence.
Steps
- Board.
specweave task list: every task must bedoneorskipped. Anything open goes back to sw-do, orspecweave task skip T-04 --reason "<why>". - Verify.
specweave verifyruns the project's test, lint and build commands (configtesting.commands, else detected), checks every acceptance criterion against the ledger (an AC is met when all its tasks are done) and writesreports/verify.mdandreports/verify.json. Red: fix and re-run. Do not tick AC boxes; they are derived. - Review. For anything that ships, run sw-review in a fresh context. With
review.crossModelon, alsospecweave review: another model family reviews the diff (exit 3 means fix first). If the project has aGLOSSARY.md, runspecweave glossary checkand rename new code that uses an avoided word. Fix critical and high findings, then verify again. - Docs. If commands, config or user-facing behaviour changed, update README,
CHANGELOG and the
## Commandstable in AGENTS.md in the same branch. - Complete.
specweave complete 0042. It refuses without a passing verify unless the user gives a reason:specweave complete 0042 --reason "<why>". - Ship. Push the branch and open the PR the way this repository ships;
specweave reportwrites an HTML timeline to attach as evidence.
Report in one paragraph: verify result, review verdict (or "skipped"), commits, anything deferred.
Manual path (no CLI)
Check every task in spec.md has a done or skip line in ledger.jsonl. Run the
project's test, lint and build commands yourself and put their real output in
reports/verify.md. Then set "status": "completed" in metadata.json, the one state
change the manual path makes by hand.
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.
- 6d ago Changed · +3 lines 0efe653208d2
- 28d ago Changed · +7 lines · +45 tokens per session 4f9aebed1d11
- 1mo ago First seen · 42 lines · 0 tokens per session scan A cfe09f264af5
done is a skill published in the GitHub repository anton-abyzov/specweave (167 stars, last pushed today), licensed MIT. It adds 45 tokens to every session and 695 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
product
Consolidated Galyarder Framework Product intelligence bundle.
diet-remove
Remove a dependency identified by uzomuzo diet — analysis + issue (default) or direct PR.
review-story
QA gate for a story — verdict PASS/CONCERNS/FAIL/WAIVED + lifecycle transition. Use when: review story, qa gate, qa-gate, /review-story.
aiox-review-story
QA gate for a story — verdict PASS/CONCERNS/FAIL/WAIVED + lifecycle transition. Use when: review story, qa gate, qa-gate, /review-story.
acceptance
Test a PR review end to end and prove it honoured every guarantee in INVARIANTS.md. Use when asked to test/validate a review of a pull request, to check a finished run, or to run the 3-provider x 2-runtime acceptance matrix. Drives pr-review verify and scripts/acceptance.mjs — never hand-checks the guarantees.
intent-verify
Verify current requirements against implementation and actual results across a product or change scope, including completed features. Run permissible existing checks and report findings without fixes.