specweave AGENTS.md

specweave AGENTS.md is an instructions file for Codex, OpenCode from anton-abyzov/specweave. It costs 4,050 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 CodexOpenCode

Install

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.

agentmods
npx agentmods add instructions/anton-abyzov/specweave/agents-md
Clone the repo
git clone --depth 1 https://github.com/anton-abyzov/specweave

Made for: 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.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.svg" alt="Measured on agentmods" height="20"></a>
Per session 4,050 This file is loaded in full into every session.
When invoked 4,050 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
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 $0.04050 $0.04050
Opus 5 $0.02025 $0.02025
Sonnet 5 $0.00810 $0.00810
Haiku 4.5 $0.00405 $0.00405

Measured 5d ago against content hash c6301f38334e, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, 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 · 447 lines

How it starts

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

Essential Rules

1. NEVER pollute project root with .md files
2. Increment IDs unique (0001-9999)
3. ONLY 4 files in increment root: metadata.json, spec.md, plan.md, tasks.md
4. ALL reports/scripts/logs → increment subfolders (NEVER at root!)
5. metadata.json MUST exist BEFORE spec.md can be created
6. tasks.md + spec.md = SOURCE OF TRUTH (update after every task!)
7. EVERY User Story MUST have **Project**: field
8. For 2-level structures: EVERY US also needs **Board**: field

Increment Folder Structure

.specweave/increments/0001-feature/
├── metadata.json                  # REQUIRED - create FIRST
├── spec.md                        # WHAT & WHY
├── plan.md                        # HOW (optional)
├── tasks.md                       # Task checklist
├── reports/                       # ALL other .md files go here!
├── scripts/                       # Helper scripts
└── logs/                          # Execution logs
    └── 2026-01-04/

Workflow Orchestration

1. Plan Before Code

BEFORE implementing ANY non-trivial task (3+ steps):

  1. Create increment: spec.md (WHAT/WHY) + plan.md (HOW) + tasks.md (checklist)
  2. Get user approval before implementing
  3. If something goes sideways → STOP and re-plan

See Task Format and User Story Format sections for templates.

2. Verify Before Done

Never mark a task complete without proving it works:

  • Code compiles/builds successfully
  • Tests pass
  • Acceptance criteria actually satisfied
  • Ask: "Would a staff engineer approve this?"

3. Dependencies First

Satisfy dependencies BEFORE dependent operations.

Bad:  node script.js → Error → npm run build
Good: npm run build → node script.js → Success

Read the full file on GitHub · 447 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 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 (159 stars, last pushed today), licensed MIT. It adds 4,050 tokens to every session, about $0.0202 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-08-30.

Related

Other instructions, from other repositories