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-syncgit 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-sync)<a href="https://agentmods.dev/skills/obsidian-owl/specwright/sw-sync"><img src="https://agentmods.dev/badge/skills/obsidian-owl/specwright/sw-sync/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-sync"><img src="https://agentmods.dev/badge/skills/obsidian-owl/specwright/sw-sync.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.00036 | $0.01145 |
| Opus 5.5 | $0.00014 | $0.00458 |
| Sonnet 5.5 | $0.00007 | $0.00229 |
| Haiku 4.5 | $0.00004 | $0.00114 |
Grade A, and why
sw-sync 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 — 124 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Specwright Sync
Goal
Keep the local repository current without deleting branches that are still claimed by a live Specwright session or a subordinate helper worktree.
Inputs
{projectArtifactsRoot}/config.json{worktreeStateRoot}/session.json{repoStateRoot}/work/*/workflow.jsongit worktree list --porcelain
Outputs
- Remotes fetched and pruned
- Base branch fast-forwarded when safe
- Candidate stale branches previewed, then deleted only after confirmation
- Summary report: branches fetched, removed, skipped, protected, and any stale active works detected
Advisory Reporting
- After fetch/prune completes,
sw-syncmay report stale active works against their recorded targets and latest known freshness state. - This report is advisory only and does not take ownership of reconcile-or-ship decisions away from the lifecycle skills.
sw-syncnever rebases, merges, retargets, or clears a freshness block on behalf ofsw-build,sw-verify, orsw-ship.
Constraints
Fetch (HIGH freedom):
- Run
git fetch --all --prune.
State-aware protection set (LOW freedom):
- Build a branch protection set from:
- the currently checked out branch
- the configured base branch and perennial branches
- branches recorded by live
session.jsonfiles acrossgit worktree list - branches recorded in attached work
workflow.json.branch - helper branch patterns
worktree-*andspecwright-wt-*
- Treat subordinate helper worktrees discovered via
git worktree list --porcelainas protected branch owners even when they are not user-facing sessions. - Never delete a branch that appears in that protection set.
Stale branch detection (HIGH freedom):
- Primary signal:
git branch -vventries with[gone] - Supplementary signal:
git branch --mergedagainst the configured base branch - Do not promote a branch to deletion solely because it is merged if a live session still references it.
- Do not delete a branch when a live session or subordinate helper still claims it.
- Classify confirmed stale branches into:
safe-deletefor branches that should still usegit branch -dforce-delete-candidatefor[gone]branches only when they are not protected, not invalid, and not claimed by a live session or subordinate helper worktree
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 · 124 lines · 36 tokens per session scan A f7f31769d992
sw-sync is a skill published in the GitHub repository Obsidian-Owl/specwright (10 stars, last pushed 5mo ago), licensed MIT. It adds 36 tokens to every session and 1,145 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
release
Cut a brooks-lint release: set the version in package.json, propagate it across all four plugin manifests and every version-bearing text file (README badges, docs site metadata), write the CHANGELOG entry, validate, then commit, push, tag, and publish the GitHub release. Triggers when the maintainer asks to "release"…
procoder
Work like a senior developer in a repository governed by procoder: run the commit gate before calling anything done, format and lint through the binary, and drive the spec, plan, todo, backlog, and sprint chain in .procoder/. Use this skill when the repository contains a .procoder/ directory or an AGENTS.md naming…
git-workflow
Manages branches, worktrees, atomic commits, and branch completion by merge, PR, preserve, or discard. Use when starting feature work that needs a branch or an isolated workspace, making commits during development, or finishing a development branch. Also use when the user says "set up worktree", "create PR", "finish…
shipyard-verification
Requires fresh verification evidence before any claim that work is complete, fixed, or passing. Use before committing, creating PRs, or moving to the next task. Also use when a status report contains words like "should", "probably", or "seems to", or expresses satisfaction ("Great!", "Done!") before verification…
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…
pr-feedback
Work a reviewer's comments on a pull request to the end - all three comment surfaces enumerated before any is triaged, every comment fixed, declined with a reason, or ticketed, push before you reply. Use when a PR comes back with review feedback or a red check.