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/setupnpx skills add ShipWithAI/shipwithai-plugins --skill setupgit 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.00099 | $0.01392 |
| Opus 5 | $0.00049 | $0.00696 |
| Sonnet 5 | $0.00020 | $0.00278 |
| Haiku 4.5 | $0.00010 | $0.00139 |
Grade A, and why
setup 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 — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Spring Boot Toolkit — Setup
Installs the enforcement layer into the project's .claude/ so it is committed
and shared with the whole team — a teammate who clones the repo gets the guardrails
even without installing this plugin. The authoring skills (jpa-entity,
spring-rest-endpoint, db-migration) stay plugin-provided and are not copied.
Plugin source root (where templates live): the directory containing this skill's
parent, i.e. plugins/java-backend-toolkit/. Resolve files relative to it.
Step 1 — Verify this is a Spring Boot + JPA project
Confirm at least one of:
pom.xmlcontainingspring-boot-starter, orbuild.gradle/build.gradle.ktscontainingspring-boot.
And JPA in use: spring-boot-starter-data-jpa (or jakarta.persistence / javax.persistence imports).
If not a Spring Boot + JPA project → stop and say so. This toolkit's v1 paved road is Spring Boot 3.x + Spring Data JPA only (no Kotlin, reactive, or non-Spring).
Step 2 — Detect project slots (smart defaults, confirm — do not interrogate)
Scan, propose, ask only to confirm:
| Slot | Detect from | Default if absent |
|---|---|---|
MIGRATION_TOOL |
flyway-core dep or src/main/resources/db/migration/ → Flyway; liquibase-core → Liquibase |
Flyway |
BASE_ENTITY |
a @MappedSuperclass class and/or AuditingEntityListener usage |
a @MappedSuperclass BaseEntity with Spring Data JPA auditing |
PROJECT_NAME |
CLAUDE.md identity / repo dir name | repo directory name |
| strict mode | --strict arg |
jpql-injection blocks (already the default in guardrails-config.json) |
Show the resolved slot values in one block and get a single confirmation.
Step 3 — Install the guardrail hook (copy flat into .claude/hooks/)
Copy these three files from the plugin's hooks/ and rules/ into the project's
.claude/hooks/ (flat — the hook finds its ruleset beside itself):
hooks/jpa-guardrail.py→.claude/hooks/jpa-guardrail.pyrules/ruleset.json→.claude/hooks/ruleset.jsonhooks/guardrails-config.json→.claude/hooks/guardrails-config.json
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.
- 2d ago First seen · 114 lines · 99 tokens per session scan A 3710f0e1e5c6
setup is a skill published in the GitHub repository ShipWithAI/shipwithai-plugins (10 stars, last pushed 20d ago), licensed MIT. It adds 99 tokens to every session and 1,392 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-задач вне автопилота.