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/initnpx skills add ShipWithAI/shipwithai-plugins --skill initgit clone --depth 1 https://github.com/ShipWithAI/shipwithai-pluginsWhat 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.00096 | $0.03513 |
| Opus 5 | $0.00048 | $0.01757 |
| Sonnet 5 | $0.00019 | $0.00703 |
| Haiku 4.5 | $0.00010 | $0.00351 |
Grade A, and why
init 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 2d 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 — 386 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/init
Mandatory entry point for the plugin. Do not run any other skill before init completes.
Instructions
Step 1 — State Detection
Before any other detection, check for an empty directory:
Scan for: package.json, pom.xml, build.gradle, go.mod, Cargo.toml,
pyproject.toml, Gemfile, composer.json, mix.exs
If NONE of these files are found:
"This looks like an empty project. Handing you off to
/shipwithai-starter:new-project for a better setup experience."
→ invoke /shipwithai-starter:new-project
→ stop
If stack files are found, continue with normal state detection:
Before asking anything, read the project state:
CLAUDE.md → populated / has [PLACEHOLDER] / missing
.claude/settings.json → exists / missing
.mcp.json → exists / missing
.claude/agents/ → exists / missing
docs/architecture.md → exists / missing
Auto-detect tech stack:
package.json → Node/TypeScript
pyproject.toml → Python
go.mod → Go
Cargo.toml → Rust
pom.xml / build.gradle → Java
Gemfile → Ruby
Detect existing tools:
.eslintrc* / eslint.config.* → ESLint
prettier.config* / .prettierrc → Prettier
jest.config* → Jest
pytest.ini / conftest.py → pytest
Makefile → make
docker-compose.yml → Docker Compose
If --update is provided: skip to Update Mode below — do not run the full interview.
If CLAUDE.md is already populated and --redo is not set and --update is not set: "Harness is already set up. Want to redo? (use --redo) or answer new questions only? (use --update)"
If --tier argument is provided, skip the tier selection prompt in Step 2 and use the given value directly.
Update Mode (--update)
Run when review detects schema is outdated, or user runs init --update directly.
Step 1: Read .claude/starter-context.json
→ Not found: "No context found. Run /shipwithai-starter:init for full setup."
→ Found: continue
Step 2: Compare existing fields against current schema (v1.4)
→ Find all fields that are null or absent
Step 3: For each missing field, ask the corresponding interview question only
→ Same wording as full interview
→ Skip all fields that already have answers
Step 4: Update starter-context.json
→ Merge new answers in
→ Set version to "1.4"
Step 5: Invoke setup-memory (merge mode)
→ Adds/updates only sections with new data
→ Existing sections preserved
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.
- 2d ago First seen · 386 lines · 96 tokens per session scan A bf20e389883d
init is a skill published in the GitHub repository ShipWithAI/shipwithai-plugins (10 stars, last pushed 20d ago), licensed MIT. It adds 96 tokens to every session and 3,513 once invoked, about $0.0005 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
rulesync
Generates and syncs AI rule configuration files (.cursorrules, CLAUDE.md, copilot-instructions.md) across 20+ coding tools from a single source. Use when syncing AI rules, running rulesync commands, importing or generating rule files, or managing shared AI coding configurations.
establishing-project-context
Use when the user asks to establish shared project language, or project work exposes a conflicting, renamed, or deprecated domain term that needs active semantic modeling. Routine small tasks stay on the fast path.
autoprompt
Explicit-only useful-first orchestration. Invoke /autoprompt to turn a mission into one executable roadmap, build dependency-safe lanes, and verify the result with independent reviewers. Never infer invocation from ordinary requests. Never resume from leftover artifacts without an explicit resume instruction.
memstack-business-gdpr
Use this skill when the user says 'GDPR', 'data protection', 'privacy compliance', 'DPA', 'DSAR', 'data subject request', 'cookie consent', 'privacy audit', 'CCPA', or asks 'do I need GDPR for this repo'. Scans the repository to detect what personal data is collected, classifies sensitivity, determines whether GDPR…
echo
Use when the user references past sessions, asks 'what did we do', 'do you remember', 'last session', 'recall', or 'continue from'.
backend-builder
Используй только внутри активного Codex Project Autopilot-проекта по утверждённому плану; не включай для обычных backend-задач вне автопилота.