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 instructions/shipwithai/shipwithai-plugins/claude-mdgit 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/instructions/shipwithai/shipwithai-plugins/claude-md)<a href="https://agentmods.dev/instructions/shipwithai/shipwithai-plugins/claude-md"><img src="https://agentmods.dev/badge/instructions/shipwithai/shipwithai-plugins/claude-md.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.01321 | $0.01321 |
| Opus 5 | $0.00660 | $0.00660 |
| Sonnet 5 | $0.00264 | $0.00264 |
| Haiku 4.5 | $0.00132 | $0.00132 |
Grade A, and why
shipwithai-plugins CLAUDE.md 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 — 147 lines — stays where its author put it; the contents beside it link to each section on GitHub.
shipwithai-plugins — Claude Context
Generated by /shipwithai-starter on 2026-05-28. Edit directly — every skill reads this before doing anything.
Project identity
Name: shipwithai-plugins Type: Monorepo Team size: 1 developer Stage: Active
Tech stack
Language(s): Markdown + JSON (plugin authoring) Framework(s): ShipWithAI Claude Code plugin standard Build tool: None Test framework: None (evals/evals.json per skill) Package manager: None Safety hooks: Python 3 (stdlib only)
Architecture overview
Style: Monorepo — one directory per plugin
Key layers:
- Plugin layer:
plugins/<plugin-name>/— one Claude Code plugin per directory - Skills layer:
plugins/<plugin-name>/skills/<skill-name>/— SKILL.md + assets + references + evals - Hooks layer:
.claude/hooks/— validate-command.py, protect-files.py, observe.py - Docs layer:
docs/— architecture, ADRs, CODEMAPS - Scripts layer:
scripts/— publish-plugin.sh for releasing plugins
Entry points:
plugins/*/manifest.json— Claude Code reads this to discover skills
Key directories:
shipwithai-plugins/
├── plugins/
│ └── <plugin-name>/
│ ├── skills/<skill-name>/
│ │ ├── SKILL.md ← 500-line hard cap
│ │ ├── assets/ ← templates for user codegen (handle with care)
│ │ ├── references/ ← lazy-loaded reference docs (< 300 lines)
│ │ └── evals/evals.json ← 5+ test prompts
│ ├── manifest.json ← skill registry (must stay in sync)
│ ├── plugin.json ← plugin metadata
│ ├── CHANGELOG.md
│ └── README.md ← live SSOT, update after every change
├── .claude/
│ ├── settings.json
│ ├── starter-context.json
│ └── hooks/ ← validate-command.py, protect-files.py, observe.py
├── docs/
│ ├── ARCHITECTURE.md
│ ├── adr/ ← Architecture Decision Records
│ ├── CODEMAPS/ ← codebase navigation guide
│ ├── starter/ ← starter plugin PRDs and specs
│ └── superpowers/ ← plans and specs for superpowers skills
│ ├── plans/
│ └── specs/
└── scripts/
└── publish-plugin.sh ← always confirm before running
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 · 147 lines · 1,321 tokens per session scan A 3fc95e363bc7
shipwithai-plugins CLAUDE.md is an instructions file published in the GitHub repository ShipWithAI/shipwithai-plugins (10 stars, last pushed 23d ago), licensed MIT. It adds 1,321 tokens to every session, about $0.0066 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 instructions, from other repositories
cc-multi-cli-plugin AGENTS.md
Instructions for greenpolo/cc-multi-cli-plugin, covering agents.md, what this is, the golden rule, the request chain and build & test.
coco-workflow CLAUDE.md
Instructions for skullninja/coco-workflow, covering claude.md -- coco, project overview, architecture, key files and tracker (lib/tracker.sh).
agent-toolkit AGENTS.md
AGENTS.md instructions for DiUS/agent-toolkit, covering agents.md, what this repo is, repo map, principles and how to add each component type.
agentic-tech-debt AGENTS.md
AGENTS.md instructions for bcanfield/agentic-tech-debt: The agent instructions for this repo live in CLAUDE.md — one source of truth for every coding agent. Read it and follow it as written; it applies to Codex exactly as it does to Claude Code.
zuvo CLAUDE.md
Claude Code instructions for greglas75/zuvo, covering zuvo plugin — project guide, what this repo is, tech stack, how to update after making changes and for yourself (dev testing, no marketplace push).
plumber copilot-instructions.md
Instructions for akshatnerella/plumber: You are a plumber. A plumber fixes the pipe — not the floor. The best fix makes the problem impossible.