Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/XyDisorder/shipjawnpx agentmods add skills/xydisorder/shipjaw/shipjaw-adoptWrote 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/xydisorder/shipjaw/shipjaw-adopt)<a href="https://agentmods.dev/skills/xydisorder/shipjaw/shipjaw-adopt"><img src="https://agentmods.dev/badge/skills/xydisorder/shipjaw/shipjaw-adopt/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/xydisorder/shipjaw/shipjaw-adopt"><img src="https://agentmods.dev/badge/skills/xydisorder/shipjaw/shipjaw-adopt.svg" alt="Reviewed on agentmods" width="80" 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.00000 | $0.01868 |
| Opus 5 | $0.00000 | $0.00934 |
| Sonnet 5 | $0.00000 | $0.00374 |
| Haiku 4.5 | $0.00000 | $0.00187 |
Grade A, and why
shipjaw-adopt 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 3d 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 — 178 lines — stays where its author put it; the contents beside it link to each section on GitHub.
shipjaw-adopt
Adopt only. Bring an existing app under the Shipjaw continuation contract without re-scaffolding or rewriting the product by default.
After adopt → use shipjaw-ask (including the proposed arch
convergence phase). Never run shipjaw-build on a non-empty app that
already has product code.
Templates / kit: ../shipjaw-build/templates/ ·
../shipjaw-build/templates/scaffold/ ·
../shipjaw-build/templates/technical-plan-converge-arch.md.
Complete Shipjaw KB already: shipjaw-ask + migration — not a full
re-adopt.
Anti-triggers
- No app yet / empty folder →
/shipjawthen prompt/build - Rough idea only →
shipjaw-prompt - Complete Shipjaw KB already (
documentation/INDEX.md+knowledge-base/architecture.md+features-index.md) →shipjaw-ask(migration upgrades if needed). Partial docs → stay here and merge (never wipe). - Non-TypeScript repo → refuse
- User wants a full rewrite / new Next app →
shipjaw-buildin a new folder, not adopt-in-place
Checklist
- [ ] Detect TS/Next app
- [ ] ./scripts/survey-adopt-state.sh <root> (read fully, incl. arch signals)
- [ ] Classify: NO_DOCS | PARTIAL_DOCS | FULL_SHIPJAW_KB
- [ ] If FULL → stop; hand off shipjaw-ask
- [ ] ≤2 clarify Q only for gaps survey couldn't answer
- [ ] init-docs-skeleton (idempotent)
- [ ] Absorb foreign plans → roadmap / features-index / decisions / changelog
- [ ] Architecture practice audit (read-only) → gaps table in architecture.md
- [ ] Propose converge-arch phase (plan only; no mass refactor)
- [ ] copy-continuation-contract + stamp-provenance --adopted
- [ ] Tooling gaps idempotent
- [ ] validate-docs + validate-docs-drift + run-gate (cheap)
- [ ] Write documentation/handoff.md (next /shipjaw-ask … + arch P0)
- [ ] Status snapshot + improvement plan summary + /shipjaw-ask handoff
Workflow
1. Detect + survey (mandatory)
../shipjaw-build/scripts/survey-adopt-state.sh <project-root>
Read all sections, including architecture practice signals and the
gate baseline (lint/typecheck). A pre-existing baseline failure isn't
this adopt's fault — record it as an architecture.md gap (not a P0/P1
architecture row, its own line) so nobody mistakes it for a regression
later, and so a future run-gate.sh run isn't a surprise.
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.
- 3d ago Changed d429c777595d
- 11d ago First seen · 178 lines · 0 tokens per session scan A 39481ea62c76
shipjaw-adopt is a skill published in the GitHub repository XyDisorder/shipjaw (2 stars, last pushed 3d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,868 tokens. 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
issue-creation
Trigger: issue creation, bug reports, feature requests, or issue approval. Create and triage GitHub issues from repository evidence.
sdd-tasks
Break an SDD change into implementation tasks. Trigger: orchestrator launches task planning for a change.
mission-control
Interact with Mission Control — AI agent orchestration dashboard. Use when registering agents, managing tasks, syncing skills, or querying agent/task status via MC APIs.
systemic-issue-triage
Trigger: new issue, bug report, triage, backlog, issue flood, community report, root cause, dead-end, blocked user. Attack issues by root class, never one-by-one; fixes must shrink the system, not grow it.
init-workspace-flow
Workflow for initializing or upgrading a workspace: context, discovery, documentation, etc.
arrange-workspace-flow
Workflow for arranging a workspace: layout, reference source code, business/technical context, ecosystem setup.