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/reviewnpx skills add ShipWithAI/shipwithai-plugins --skill reviewgit 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/review)<a href="https://agentmods.dev/skills/shipwithai/shipwithai-plugins/review"><img src="https://agentmods.dev/badge/skills/shipwithai/shipwithai-plugins/review.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.00059 | $0.02713 |
| Opus 5 | $0.00030 | $0.01357 |
| Sonnet 5 | $0.00012 | $0.00543 |
| Haiku 4.5 | $0.00006 | $0.00271 |
Grade A, and why
review 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 — 220 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/review
Audit full harness health. Detect drift. Suggest next actions.
Flag Handling
--drift-only— skip component scoring (Step 1), run drift detection only (Step 2)--tier-check— skip drift detection (Step 2), show current tier and what is missing for the next tier upgrade
Step 1 — Score Components
Read and score each component:
starter-context.json → version current (1.4) ✅ / outdated ⚠️ / missing ❌
CLAUDE.md → populated ✅ / has-placeholder ⚠️ / missing ❌
CLAUDE.md workflow → present ✅ / opted-out ✅ / missing ⚠️
.claude/settings.json → configured ✅ / exists-empty ⚠️ / missing ❌
settings.json hooks → hooks configured ✅ / empty ⚠️ / missing ❌
.mcp.json → servers configured ✅ / exists-empty ⚠️ / missing ❌
.claude/agents/ → agents present ✅ / missing ❌
docs/architecture.md → exists ✅ / missing ❌
docs/adr/ → ADRs present ✅ / index-only ⚠️ / missing ❌
.claude/memory/ → lifecycle complete ✅ / legacy-layout ⚠️ / incomplete ⚠️ / missing ❌ (Tier 3)
✅ lifecycle: MEMORY.md + HANDOFF.md + decisions/ + conventions/ +
load-memory.sh & remind-save.sh hooks + .claude/skills/save-memory/
⚠️ legacy: project.md / team.md present (pre-2.4.0 static memory) → offer migration
⚠️ incomplete: .claude/memory/ exists but hooks or /save-memory missing
.claude/hooks/observe.py → present ✅ / missing (Tier 3 opt-in) ❌
.claude/logs/ in .gitignore → in gitignore ✅ / tracked by git ⚠️ / not applicable ✅
Schema version check:
Read .claude/starter-context.json:
→ not found → ❌ not initialized
→ version == "1.4" → ✅ current
→ version == "1.3" → ⚠️ outdated — run init --update (adds stack_plugins_selected field)
→ version == "1.2" → ⚠️ outdated — run init --update (adds skills_selected, stack_plugins_selected)
→ version < "1.2" or absent → ⚠️ outdated — run init --update
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.
- 6d ago First seen · 220 lines · 59 tokens per session scan A c1f65c82a21f
review is a skill published in the GitHub repository ShipWithAI/shipwithai-plugins (10 stars, last pushed 24d ago), licensed MIT. It adds 59 tokens to every session and 2,713 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.