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 skills/obsidian-owl/specwright/sw-pivotnpx skills add Obsidian-Owl/specwright --skill sw-pivotgit 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-pivot)<a href="https://agentmods.dev/skills/obsidian-owl/specwright/sw-pivot"><img src="https://agentmods.dev/badge/skills/obsidian-owl/specwright/sw-pivot.svg" alt="Measured on agentmods" 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.00029 | $0.01628 |
| Opus 5 | $0.00015 | $0.00814 |
| Sonnet 5 | $0.00006 | $0.00326 |
| Haiku 4.5 | $0.00003 | $0.00163 |
Grade A, and why
sw-pivot 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 6d 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 — 150 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Specwright Pivot
Goal
Research-backed rebaselining for the selected work. Capture preserved scope,
understand what changed, classify the pivot, revise the affected open work via
architect, and hand back to /sw-plan or /sw-build as appropriate. Applies
protocols/decision.md for all decisions. Revisions auto-applied and recorded
in decisions.md; the revised artifact set is the contract.
Inputs
{worktreeStateRoot}/session.json— selected work for this worktree{repoStateRoot}/work/{selectedWork.id}/workflow.json— selected work state, active unit,tasksCompleted,tasksTotal, and work/unit paths- work-level artifacts:
design.md,context.md,assumptions.md,decisions.md,integration-criteria.mdwhen present - active or affected unit artifacts:
spec.md,plan.md,context.md {workArtifactsRoot}/{selectedWork.id}/approvals.md— durable approval ledger for design and unit lineage- Pivot reason (argument or conversation)
- Optional recent retro or research inputs when available and relevant
Outputs
- revised work-level artifacts when design or scope changes require them
- regenerated affected remaining-unit artifacts when unit boundaries or observable behavior change
- updated
integration-criteria.mdwhen structural pivots stale the current criteria - selected work's
workflow.json— pivot classification, active state, and affected remaining work updated decisions.md— pivot decisions recorded
Constraints
Pre-condition (LOW freedom):
Resolve the selected work from the current worktree session. Valid entry states
are planning, building, and verifying. Reject designing,
shipping, and shipped with explicit guidance: use /sw-design change
request flow for designing, and start a fresh work or normal ship/fix flow
for shipping or shipped. If another live top-level worktree owns the
selected work, STOP with explicit adopt/takeover guidance.
Snapshot (LOW freedom): Read the selected work's completed and open scope. Present preserved baseline scope versus delta scope before proposing any mutation.
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.
- 6d ago First seen · 150 lines · 29 tokens per session scan A 267646f6033b
sw-pivot is a skill published in the GitHub repository Obsidian-Owl/specwright (9 stars, last pushed 4mo ago), licensed MIT. It adds 29 tokens to every session and 1,628 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.
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
Import a spec-kit feature spec into Shipyard, replacing brainstorming. Use when a spec-kit feature directory exists with spec.md.
worktree
Isolate work in a git worktree. Activates when the user needs branch isolation before executing a plan, wants a clean environment for a feature, is ready to finish work in an existing worktree, or wants to reclaim worktrees that accumulated and are now polluting filesystem-level measurement.
write-article
Write high-quality articles from scratch using a 6-phase pipeline: deep STORM-inspired research with parallel agents, multi-perspective outline generation, section-by-section drafting with research grounding, adaptive anti-slop enforcement (hard/soft banned vocabulary per tone), cross-model adversarial review, and SEO…