specweave: Instructions file for Claude Code

AGENTS.md

specweave AGENTS.md is an instructions file for Claude Code, Codex, OpenCode from anton-abyzov/specweave. It costs 1,511 tokens per session, scanned A, original, MIT.

Instructions for SpecWeave, a project-planning workflow that stores each feature in a numbered increment folder with specifications, plans, tasks, and reports. They define the required files, naming rules, and order of work.

In plain words
What is it for?
Use them before implementing a substantial feature, when creating or updating an increment, when requesting approval for a plan, and when verifying completed work.
Why use it?
They keep planning documents organized and make the specification and task list the shared record of what should be built and what has been completed.

Instructions file for Claude CodeCodexOpenCode

Written for Claude Code and Codex and OpenCode: SessionStart hook event, but also the file is AGENTS.md. Also seen: mentions subagents; mentions Claude Code; mentions AGENTS.md.

This is anton-abyzov/specweave's own configuration. It tells Claude Code, Codex and OpenCode how to work on specweave itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything specweave configures →

Reuse

Borrowing it

Nothing to install: this file belongs to anton-abyzov/specweave. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/anton-abyzov/specweave/develop/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/anton-abyzov/specweave

Made for: Claude Code, Codex, OpenCode.

Wrote 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.

agentmods badge for specweave AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/anton-abyzov/specweave/agents-md/github.svg)](https://agentmods.dev/instructions/anton-abyzov/specweave/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/anton-abyzov/specweave/agents-md"><img src="https://agentmods.dev/badge/instructions/anton-abyzov/specweave/agents-md/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.

agentmods 80×15 button for specweave AGENTS.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/anton-abyzov/specweave/agents-md"><img src="https://agentmods.dev/badge/instructions/anton-abyzov/specweave/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 1,511 This file is loaded in full into every session.
When invoked 1,511 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.01511 $0.01511
Opus 5.5 $0.00604 $0.00604
Sonnet 5.5 $0.00302 $0.00302
Haiku 4.5 $0.00151 $0.00151

Measured 5d ago against content hash 8054e9aae5b4, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

specweave AGENTS.md 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 5d 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.

AGENTS.md · 56 lines

How it starts

The opening of the file, as written. The whole thing — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.

SpecWeave (this repository)

This is the source of the specweave npm package: a CLI plus a Claude Code plugin that plans work as increments (spec.md + ledger.jsonl) and hands it between AI tools. This file is for anyone changing SpecWeave itself; the file SpecWeave writes into user projects is src/templates/AGENTS.md.template.

Layout

Path What it is
bin/specweave.js Commander entry; each command lazily imports dist/src/cli/commands/<name>.js
src/cli/commands/ One file per CLI command
src/core/tasks/ Task parser, ledger.jsonl fold, task board, verify, AC derivation
src/core/session/ pickup, handoff (doc, Git capture, --push, secret scrub)
src/core/increment/ Increment creation, metadata, status transitions
src/core/hooks/handlers/ Claude Code hook handlers, reached through plugins/specweave/hooks/run.mjs
src/sync/, src/integrations/ GitHub, Jira and ADO sync (opt-in, only on specweave sync)
src/templates/ What init and update write into user projects
skills/sw-* The one skill source for every tool; npm run generate:skills writes the plugin copies in plugins/specweave/skills/ (never edit those)
docs-site/ spec-weave.com (Docusaurus); deploys from develop

Work here

  • Node 22. npm ci, then npm run build (tsc, dashboard, plugin copies). The CLI runs from dist/, so rebuild before trying a command: node bin/specweave.js <cmd>.
  • Tests: npm run test:unit is what CI runs (tests/unit/**). Co-located src/**/*.test.ts files are not in CI; run them with npx vitest run src/<path> when you touch that code, and put new tests under tests/unit/.
  • Typecheck with npx tsc --noEmit -p . before pushing.
  • Adding or renaming a CLI command or option: regenerate completions with node scripts/completions/generate.mjs.
  • init refuses to run inside the system temp directory; use a scratch folder elsewhere to try it.
  • Keep files under 1,500 lines. Prefer deleting code to adapting it.
  • Default branch is develop. PRs target develop.
  • Browser tests and automation must use headless Chrome/Playwright CLI. Set headless: true, PWDEBUG=0, PLAYWRIGHT_HTML_OPEN=never, and HTML reports open: 'never'. Save captures to files and pass this rule to subagents. If a visible browser is essential, ask the user and wait for explicit approval before opening it; a headless failure is not approval.

Read the full file on GitHub · 56 lines

Changes

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.

  1. 5d ago Changed · +2 lines · +249 tokens per session 8054e9aae5b4
  2. 7d ago Changed · +10 lines · +168 tokens per session f0e72812297c
  3. 8d ago Changed · +1 lines · +86 tokens per session 471430c637b1
  4. 13d ago Changed · +2 lines · +89 tokens per session 4d1908ed44bc
  5. 18d ago Changed · +1 lines · +118 tokens per session cf573627e0cf
  6. 26d ago Changed · -385 lines · -3,149 tokens per session 5b894fd24e43
  7. 1mo ago Changed · -22 lines · -100 tokens per session 7ce1a77077c1
  8. 1mo ago First seen · 447 lines · 4,050 tokens per session scan A c6301f38334e

Subscribe to this mod's changes

specweave AGENTS.md is an instructions file published in the GitHub repository anton-abyzov/specweave (166 stars, last pushed today), licensed MIT. It adds 1,511 tokens to every session, about $0.0060 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-08-30.

Related

Other instructions, from other repositories

vscode buildNext.instructions.md

Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).

microsoft/vscode · 9,649 tokens

next.js AGENTS.md

AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js · 7,384 tokens

vscode oss-third-party-notices.instructions.md

Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).

microsoft/vscode · 5,262 tokens

langchain AGENTS.md

AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.

langchain-ai/langchain · 4,680 tokens

vscode copilot-instructions.md

Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).

microsoft/vscode · 2,731 tokens

deno copilot-instructions.md

Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.

denoland/deno · 3,077 tokens