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/shipwithai/shipwithai-plugins/setup-ssotnpx skills add ShipWithAI/shipwithai-plugins --skill setup-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/setup-ssot)<a href="https://agentmods.dev/skills/shipwithai/shipwithai-plugins/setup-ssot"><img src="https://agentmods.dev/badge/skills/shipwithai/shipwithai-plugins/setup-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 | $0.00062 | $0.01423 |
| Opus 5 | $0.00031 | $0.00711 |
| Sonnet 5 | $0.00012 | $0.00285 |
| Haiku 4.5 | $0.00006 | $0.00142 |
Grade A, and why
setup-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 5d 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 — 204 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/setup-ssot
Configures SSOT documentation: docs/architecture.md, docs/adr/, docs/CODEMAPS/.
Mode Detection
Read .claude/starter-context.json if it exists:
- Exists: use
architecture,ssot.adr,ssot.codemapsfields — skip questions - Missing (standalone): ask which outputs to create, then gather architecture details
Flags
--architecture-only— writedocs/architecture.mdonly, skip ADR and CODEMAPS--adr— include ADR structure--codemaps— include CODEMAPS structure- Flags can be combined:
--adr --codemaps
Standalone Questions (when no context file)
Ask once, grouped:
Which outputs to create?
-
docs/architecture.md— architecture overview -
docs/adr/— ADR structure with ADR-0001 -
docs/CODEMAPS/— codebase navigation guide
For each selected output, gather:
- Project name and type (web app / API / CLI / lib)?
- Primary stack (language + framework)?
- Architecture style (monolith / microservices / modular monolith / event-driven)?
- Key layers and their directories?
- Entry points?
- External dependencies (DB, queue, cache, external APIs)?
- Directories/files that must NOT be edited manually?
- Sensitive areas requiring extra care?
Output 1: docs/architecture.md
Draft from starter-context.json.architecture (or standalone answers). Use actual paths, not generic placeholders:
# Architecture Overview
*Generated by /shipwithai-starter on [DATE]. Edit directly.*
## System overview
[Project name] is a [type] built with [stack].
Architecture style: [monolith / microservices / modular monolith / event-driven].
## Key layers
| Layer | Directory | Responsibility |
|-------|-----------|----------------|
| [API] | [src/routes/] | [HTTP handlers, validation] |
| [Service] | [src/services/] | [Business logic] |
| [Data] | [src/db/] | [Database access, ORM] |
## Entry points
- `[src/index.ts]` → [main server, port 3000]
- `[src/worker.ts]` → [background job processor]
## External dependencies
| Service | Purpose | Connection |
|---------|---------|------------|
| [PostgreSQL] | [Primary database] | [DATABASE_URL] |
| [Redis] | [Session cache] | [REDIS_URL] |
## Key directories
[paste tree output or scan result]
## What to know before touching code
[Gotchas: generated dirs, build order, sensitive areas]
What ships with it
2 files 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.
- 5d ago First seen · 204 lines · 62 tokens per session scan A 59bfdbf0e0bd
setup-ssot is a skill published in the GitHub repository ShipWithAI/shipwithai-plugins (10 stars, last pushed 22d ago), licensed MIT. It adds 62 tokens to every session and 1,423 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
claude-code-session-broker
Use when running Arcgentic V2 in Claude Code and fixed Planner, Developer, and Auditor role sessions must be coordinated through a broker.
arcgentic
Use when the user says Arcgentic, asks to use Arcgentic, or wants an idea taken through a complete plan → development → self-audit → external audit workflow in Codex.
espalier-migrate
Migrate an existing harness/espalier install to the current Espalier version — auto-detects which of v0.1→v0.2, v0.3→v0.4, v0.4→v0.5, the v0.5.3 coder-agent patch, v0.5→v0.6 (Stage 1 grill), v0.6→v0.7 (read-only /espalier-ask lane), v0.7→v0.8 (requirements approval gate), the v0.8.1 impact-analysis agent patch, the…
verify-gates
Runs the mechanical quality gates that the arcgentic state machine requires for state transitions. Invoked indirectly by transition.sh OR directly by orchestrator agent before declaring a state transition. Use when about to call transition.sh OR when manually verifying that a round artifact meets the gate criteria.…
session-mode
Use when a project has not yet stored session mode, when a user asks for complete arcgentic workflow execution, or when role identity handoff prompts are needed.
cross-session-handoff
Read, write, snapshot, and lock .arcgentic/state.yaml across planner, dev, audit, and optional test sessions.