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 autogit 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/auto)<a href="https://agentmods.dev/skills/anton-abyzov/specweave/auto"><img src="https://agentmods.dev/badge/skills/anton-abyzov/specweave/auto.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.00040 | $0.00834 |
| Opus 5 | $0.00020 | $0.00417 |
| Sonnet 5 | $0.00008 | $0.00167 |
| Haiku 4.5 | $0.00004 | $0.00083 |
Grade A, and why
auto 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 — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Auto Mode
Unattended execution. specweave auto writes a session file; the plugin's Stop
hook reads it after every turn and either blocks (with what remains) or lets the
session end. There is no daemon and no background process — the loop is the hook.
Start / inspect / stop
| Intent | Command |
|---|---|
| Start on specific increments | specweave auto 0042 0043 |
| Start on whatever is active | specweave auto |
| Preview without activating | specweave auto --dry-run |
| Clear stale session state | specweave auto --reset |
| Progress of the running session | specweave auto-status [--json] |
| Stop it (emergency) | specweave cancel-auto [--force] |
How the loop actually ends
The Stop handler decides each turn, in this order (any error → the session is released, never trapped):
- No
auto-mode.json, oractive !== true→ session over. - Session file older than
auto.maxSessionAge(default 7200 s) → released. - Turn count above
auto.maxTurns(default 20) → safety stop. stop_hook_activeand no progress for 3 consecutive turns → loop guard releases it.- No increment left to work on → released.
- Zero pending tasks and every AC satisfied → blocks once with
all_complete_needs_closure— that is your cue to close. - Otherwise → blocks with
<P> task(s) / <A> AC(s) remainand you keep going.
So: you never decide to keep looping. You do the next task, stop, and the hook either returns you or lets you go.
What you do inside the loop
specweave task next <id>→task claim→ implement inside the task'sFiles→ commit<id>: …→specweave task done T-NN <id> --run "<Test>". Same loop assw:do.- Test fails → fix it in the next turn. Never mark a task done without a passing run.
- Genuinely blocked (missing secret, ambiguous spec, external dependency) →
specweave task block T-NN <id> --note "<what is missing>"and stop. Blocked tasks do not count as remaining work, so the loop ends instead of thrashing. - On
all_complete_needs_closure:specweave verify <id>, thensw:done <id>.
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 · 66 lines · 40 tokens per session scan A e4a9664070f4
auto is a skill published in the GitHub repository anton-abyzov/specweave (159 stars, last pushed today), licensed MIT. It adds 40 tokens to every session and 834 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.