specwright: Instructions file for Codex

AGENTS.md

specwright AGENTS.md is an instructions file for Codex, OpenCode from Obsidian-Owl/specwright. It costs 1,538 tokens per session, scanned A, original, MIT.

A set of instructions for Specwright, a workflow for building applications from written specifications with review checkpoints. It covers project setup, research, design, planning, test-driven development (writing tests before implementation), building, verification, debugging, and shipping.

In plain words
What is it for?
Use it to initialize projects, research external systems, design architecture, break work into testable units, implement with TDD, investigate bugs, verify results, and prepare pull requests.
Why use it?
It gives coding agents a repeatable path from an idea to a checked implementation, while keeping decisions and requirements documented.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md. Also seen: mentions subagents; mentions Claude Code; mentions AGENTS.md.

This is Obsidian-Owl/specwright's own configuration. It tells Codex and OpenCode how to work on specwright 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 specwright configures →

Reuse

Borrowing it

Nothing to install: this file belongs to Obsidian-Owl/specwright. 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/Obsidian-Owl/specwright/main/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/Obsidian-Owl/specwright

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 specwright AGENTS.md

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

Your own site · 80×15
<a href="https://agentmods.dev/instructions/obsidian-owl/specwright/agents-md"><img src="https://agentmods.dev/badge/instructions/obsidian-owl/specwright/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 1,538 This file is loaded in full into every session.
When invoked 1,538 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.01538 $0.01538
Opus 5.5 $0.00615 $0.00615
Sonnet 5.5 $0.00308 $0.00308
Haiku 4.5 $0.00154 $0.00154

Measured 1mo ago against content hash ba2e46c0d77c, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

specwright 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 1mo 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 · 102 lines

How it starts

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

Specwright

Spec-driven app development with quality gates. Ensures the user gets what they asked for.

Compatible with AI coding agents that read AGENTS.md project instructions.

Workflow

sw-init → sw-design → sw-plan → sw-build → sw-verify → sw-ship
Skill Purpose
sw-init Project setup. Creates constitution + charter. Configures gates.
sw-research Deep outward-facing research. External docs, APIs, patterns, validation. Produces referenced briefs.
sw-design Interactive solution architecture. Research, design, adversarial critic, assumption surfacing.
sw-plan Decompose design into work units with testable specs.
sw-build TDD implementation of one work unit.
sw-verify Interactive quality gates. Shows findings, validates against spec.
sw-ship Strategy-aware merge via PR.
sw-debug Investigation-first debugging. Scope → investigate → diagnose → fix/log/defer.
sw-pivot Mid-build course correction. Revises remaining tasks via architect; append-only.
sw-doctor Read-only installation health check. 13 checks, repair hints.
sw-guard Detect stack and interactively configure guardrails.
sw-status Current state and progress.
sw-adopt Explicitly adopt an existing work into the current worktree after ownership checks.
sw-learn Post-ship capture of patterns and learnings.
sw-audit Periodic codebase health check. Finds systemic tech debt.
sw-sync Git housekeeping. Fetch, prune stale branches, sync with remote.
sw-review PR comment review. Fetch all comment types, group by status, respond inline.

Anchor Documents

Three persistent tracked documents drive all decisions. By default they live under .specwright/, the tracked projectArtifactsRoot:

  • .specwright/CONSTITUTION.md -- Development practices. How the user wants code written. The AI MUST follow these.
  • .specwright/CHARTER.md -- Technology vision. What this repo is, who consumes it, architectural invariants.
  • .specwright/TESTING.md -- Testing strategy. How the project should be tested, what boundaries exist, what may be mocked. Optional — created during init if the user opts in.

Read the full file on GitHub · 102 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. 1mo ago First seen · 102 lines · 1,538 tokens per session scan A ba2e46c0d77c

Subscribe to this mod's changes

specwright AGENTS.md is an instructions file published in the GitHub repository Obsidian-Owl/specwright (10 stars, last pushed 6mo ago), licensed MIT. It adds 1,538 tokens to every session, about $0.0062 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-31.

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,715 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,461 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