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 skills add Obsidian-Owl/specwright --skill sw-initgit clone --depth 1 https://github.com/Obsidian-Owl/specwrightWrote 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.
[](https://agentmods.dev/skills/obsidian-owl/specwright/sw-init)<a href="https://agentmods.dev/skills/obsidian-owl/specwright/sw-init"><img src="https://agentmods.dev/badge/skills/obsidian-owl/specwright/sw-init/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.
<a href="https://agentmods.dev/skills/obsidian-owl/specwright/sw-init"><img src="https://agentmods.dev/badge/skills/obsidian-owl/specwright/sw-init.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00031 | $0.02524 |
| Opus 5.5 | $0.00012 | $0.01010 |
| Sonnet 5.5 | $0.00006 | $0.00505 |
| Haiku 4.5 | $0.00003 | $0.00252 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 194 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Specwright Init
Goal
Set up Specwright in this project by understanding how the user works,
what they're building, and what quality standards they expect. Produce
configuration and anchor documents that will guide all future work. Tracked
project artifacts should be shared across developers and agent sessions via
Git; runtime session state stays local to each clone or worktree. New
interactive installs should prefer project-visible runtime roots under
.specwright-local/, while git-admin roots under .git/specwright/ remain
compatibility-only.
Inputs
- The codebase (scan for language, framework, dependencies, test runner)
- The user (ask about practices, vision, quality expectations)
Outputs
When complete, ALL of the following exist:
{projectArtifactsRoot}/config.json-- detected + configured project settings{projectArtifactsRoot}/CONSTITUTION.md-- development practices the AI must follow{projectArtifactsRoot}/CHARTER.md-- technology vision and project identity{repoStateRoot}/work/-- shared work root, initialized and empty{worktreeStateRoot}/session.json-- initialized detached top-level session for the current worktree
Optional (created if the user opts in):
{projectArtifactsRoot}/TESTING.md-- testing strategy: boundaries, infrastructure, mock allowances- Hooks set up if the user wants them
- Operator follow-up: tell the user to run
/sw-statusto confirm the active runtime roots and detached session state.
Quality gates are configured in config (all six default to enabled; user may disable).
Constraints
Worktree context (LOW freedom):
- Check
worktreeContextperprotocols/context.md. - If
linked, explain that tracked project artifacts under{projectArtifactsRoot}are shared across developers and agent sessions via Git, while runtime session state stays local to each clone or worktree under{repoStateRoot}and{worktreeStateRoot}. - If the shared layout already exists, reuse the tracked project artifacts and
shared runtime roots, then create or repair only this worktree's
{worktreeStateRoot}/session.json. - If the shared layout does not exist yet, say that
/sw-initwill create the tracked project-artifact root plus repo-level runtime state under the Git common dir and a session root for the current worktree. This is a warning, not a block.
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.
- 1mo ago First seen · 194 lines · 31 tokens per session scan A 5e02989fed2e
sw-init is a skill published in the GitHub repository Obsidian-Owl/specwright (10 stars, last pushed 5mo ago), licensed MIT. It adds 31 tokens to every session and 2,524 once invoked, about $0.0001 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.
Other skills, from other repositories
rust-skills
Rust best practices — 179 rules across 14 categories for idiomatic, optimized Rust code.
new-skill
Scaffold a new brooks-lint analysis skill so it passes npm run validate and npm run evals on the first try — generates skills/{name}/SKILL.md (with the mandatory "Do NOT trigger for:" clause and a Process section citing guide step ranges) plus skills/{name}/{name}-guide.md (sequentially numbered steps), then appends…
llm-friendly-context
Clarifies inputs, outputs, success criteria, decisions, and unresolved conditions so downstream consumers can execute without guessing. Use when writing or revising LLM-facing prompts, handoffs, planning artifacts, reviews, reports, or generated instructions.
import-spec
Imports a spec-kit feature spec into Shipyard in place of brainstorming. Use when a spec-kit feature directory with spec.md exists.
shipyard-ship
Use when delivering or releasing a completed Shipyard phase under Codex — final verification, pre-ship security audit, documentation, and release. Trigger when the user says "ship it", "ship this phase", "release this", "we're done — finalize", or "run the shipyard ship workflow". This is the Codex inline-sequential…
brainstorm
Explores a codebase, researches the problem space, and produces an approved design specification before any code is written. Use when the user wants to create a new feature, add significant functionality, redesign a subsystem, or build something that touches multiple parts of the project.