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 agentmods add instructions/obsidian-owl/specwright/agents-mdgit clone --depth 1 https://github.com/Obsidian-Owl/specwrightWhat 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 | $0.01538 | $0.01538 |
| Opus 5 | $0.00769 | $0.00769 |
| Sonnet 5 | $0.00308 | $0.00308 |
| Haiku 4.5 | $0.00154 | $0.00154 |
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 2d 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 — 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.
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.
- 2d ago First seen · 102 lines · 1,538 tokens per session scan A ba2e46c0d77c
specwright AGENTS.md is an instructions file published in the GitHub repository Obsidian-Owl/specwright (9 stars, last pushed 4mo ago), licensed MIT. It adds 1,538 tokens to every session, about $0.0077 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-31.
Other instructions, from other repositories
claude-code-sub-agent-collective CLAUDE.md
Instructions for vanzan01/claude-code-sub-agent-collective, covering claude.md, project overview, critical repository information, architecture and core system.
specs-driven-development-spring-angular production-code.instructions.md
Production code guardrails — TDD discipline and Spring Boot 4 conventions.
spec-driven-ai-development copilot-instructions.md
Instructions for LiveTrack-X/spec-driven-ai-development, covering sdad protocol, fast start, controls and route, authority and evidence and safety and execution.
agent-toolkit AGENTS.md
Instructions for eai-org/agent-toolkit, covering agent toolkit guide and docs.
gangsta GEMINI.md
Instructions for kucherenko/gangsta, a project described as: AI agentic skills framework for spec-driven development, built on the organizational model of mafia.
sugar AGENTS.md
AGENTS.md instructions for roboticforce/sugar, covering sugar - agents.md, git branching rules (strict), always create branches from develop, after work is complete and then create pr targeting develop.