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 ShipWithAI/shipwithai-plugins --skill update-ssotgit clone --depth 1 https://github.com/ShipWithAI/shipwithai-pluginsWrote 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/shipwithai/shipwithai-plugins/update-ssot)<a href="https://agentmods.dev/skills/shipwithai/shipwithai-plugins/update-ssot"><img src="https://agentmods.dev/badge/skills/shipwithai/shipwithai-plugins/update-ssot.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.00068 | $0.00943 |
| Opus 5 | $0.00034 | $0.00472 |
| Sonnet 5 | $0.00014 | $0.00189 |
| Haiku 4.5 | $0.00007 | $0.00094 |
Grade A, and why
update-ssot 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 7d 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 — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/update-ssot
Sync SSOT docs with the actual codebase. Section by section, confirm each change.
Flag Handling
--section stack— diff and update tech stack section only--section architecture— diff and update architecture/directories sections only--section conventions— diff and update coding conventions section only--section hooks— diff.claude/settings.jsonhooks vs CLAUDE.md only--section mcp— diff.mcp.jsonvs CLAUDE.md only--section all— default: diff everything- Flags can be combined:
--section stack --section mcp
Pre-flight Check
Before diffing, check which SSOT files exist:
CLAUDE.mdnot found → inform user, suggest running/shipwithai-starter:setup-ssotfirst, offer to continue anywaydocs/architecture.mdfound → include in diff scopedocs/CODEMAPS/overview.mdfound → include directories in diff scope
Step 1 — Diff SSOT vs Codebase
Run only the sections relevant to the --section flag (or all if --section all):
CLAUDE.md tech stack ←→ package.json / pyproject.toml / go.mod / Cargo.toml
CLAUDE.md key directories ←→ actual directory tree (depth 3)
CLAUDE.md build/test tools ←→ Makefile / scripts section of package.json / config files
CLAUDE.md hooks section ←→ .claude/settings.json hooks
CLAUDE.md MCP section ←→ .mcp.json mcpServers
docs/architecture.md layers ←→ actual src/ structure (if file exists)
docs/CODEMAPS/overview.md ←→ actual key directories (if file exists)
Step 2 — Report Differences
Use consistent tags. Report all differences before asking to update anything:
Found N differences:
[STACK] package.json has @tanstack/react-query 5 — not mentioned in CLAUDE.md
[DIR] src/workers/ exists — not documented in architecture section
[REMOVED] .eslintrc.json deleted — still mentioned in CLAUDE.md
[MCP] .mcp.json has Sentry server — not listed in CLAUDE.md
[ARCH] docs/architecture.md lists src/legacy/ — directory no longer exists
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 7d ago First seen · 97 lines · 68 tokens per session scan A a6430a96c514
update-ssot is a skill published in the GitHub repository ShipWithAI/shipwithai-plugins (10 stars, last pushed 24d ago), licensed MIT. It adds 68 tokens to every session and 943 once invoked, about $0.0003 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
evolution-guide
Explains how Evolving Lite works when the user asks about the system, its features, or how to use it. Triggers on questions like "how does this work", "what is evolving lite", "what hooks are running", "explain the system".
shut-up-and-code
Load-bearing comments only. Use when writing or editing code in any language, or when the user asks about comment standards.
plan-schema
Plan file (.claude/plans/-plan.md) reference — sections, per-file format, dependency graph, and converter mappings.
beads-schema
Beads (bd CLI) reference — issue types, statuses, priorities, dependencies, and common commands.
prd-schema
Skill "prd-schema" from GantisStorm/essentials-claude-code, covering when to use, conversion from plans, schema, root object and user story object.
github-cli
GitHub CLI (gh) wrapper for PR status, issues, and repository operations.