sw-init

A project-initialisation command that creates a constitution and charter, then configures project checks called gates.

In plain words
What is it for?
Use it when setting up a project for the first time and creating its tracked Specwright files and local runtime folders.
Why use it?
It provides a defined starting structure and makes the project's required checks explicit.

Command

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 commands/obsidian-owl/specwright/sw-init
Clone the repo
git clone --depth 1 https://github.com/Obsidian-Owl/specwright
Per session 12 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 97 The whole file, excluding the scripts and references it only reads on demand.
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.00012 $0.00097
Opus 5 $0.00006 $0.00048
Sonnet 5 $0.00002 $0.00019
Haiku 4.5 $0.00001 $0.00010

Measured 2d ago against content hash 0dbb9c515deb, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

sw-init 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.

adapters/codex/commands/sw-init.md · 12 lines

What it actually says

Use the installed specwright:sw-init skill for this request. Init should create tracked .specwright/ docs plus clone-local runtime roots, recommend project-visible .specwright-local/ for interactive installs, keep git-admin under .git/specwright/ as compatibility-only, and finish by pointing the operator to /sw-status.

$ARGUMENTS

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. 2d ago First seen · 12 lines · 12 tokens per session scan A 0dbb9c515deb

Subscribe to this mod's changes

sw-init is a command published in the GitHub repository Obsidian-Owl/specwright (9 stars, last pushed 4mo ago), licensed MIT. It adds 12 tokens to every session and 97 once invoked, about $0.0001 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.