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-upgradeWrote 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-upgrade)<a href="https://agentmods.dev/skills/xydisorder/shipjaw/shipjaw-upgrade"><img src="https://agentmods.dev/badge/skills/xydisorder/shipjaw/shipjaw-upgrade/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-upgrade"><img src="https://agentmods.dev/badge/skills/xydisorder/shipjaw/shipjaw-upgrade.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.00125 | $0.01087 |
| Opus 5 | $0.00063 | $0.00544 |
| Sonnet 5 | $0.00025 | $0.00217 |
| Haiku 4.5 | $0.00013 | $0.00109 |
Grade A, and why
shipjaw-upgrade 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 11d 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 — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.
shipjaw-upgrade
Upgrade only. Bring docs + continuation contract in line with the current Shipjaw skill VERSION. Does not re-scaffold the app and does not implement product features.
After upgrade → /shipjaw-ask for product work or converge-arch slices.
Principles: ../shipjaw-build/references/skill-principles.md (on
conflict only).
Migration table: ../shipjaw-build/references/migration.md.
VERSION: ../shipjaw-build/VERSION.
Delta script: ../shipjaw-build/scripts/changelog-since-stamp.sh.
Anti-triggers
- No app / empty folder →
/shipjawthen prompt/build - App with code but no
documentation/knowledge-base/→shipjaw-adoptfirst - Feature/fix request →
shipjaw-ask - Vague product idea →
shipjaw-prompt - Want a new Next app →
shipjaw-buildin a new folder
Checklist
- [ ] Confirm KB exists (else hand off adopt)
- [ ] Run changelog-since-stamp.sh → narrate delta to user
- [ ] Read VERSION + architecture scaffolded-with / adopted-with
- [ ] Apply migration.md gaps relevant to that delta (idempotent)
- [ ] copy-continuation-contract.sh (refresh AGENTS/rule if missing/stale)
- [ ] stamp-provenance.sh (refresh scaffolded-with to current VERSION)
- [ ] Ensure handoff.md exists (template); don’t invent a fake next task
- [ ] validate-docs.sh
- [ ] validate-docs-drift.sh (dangling refs + staleness since last KB touch)
- [ ] Update changelog + handoff; stop
Workflow
1. Detect + show delta
Require documentation/knowledge-base/ + preferably INDEX.md.
If missing → stop; recommend /shipjaw-adopt.
../shipjaw-build/scripts/changelog-since-stamp.sh <project-root>
Narrate from-stamp → installed VERSION and the bullet list of skill changes since the stamp (what matters for this project). If already current, say so and stop unless the user still wants a contract refresh.
2. Apply migration gaps
Follow ../shipjaw-build/references/migration.md era-specific upgrades
for everything that still applies (INDEX banner, AGENTS/rule, docs
committed, practice-gaps section, etc.). Prefer gaps implied by the
changelog delta. Idempotent: don’t overwrite custom content with blank
templates.
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.
- 11d ago First seen · 104 lines · 125 tokens per session scan A a6ad1e6cb50c
shipjaw-upgrade is a skill published in the GitHub repository XyDisorder/shipjaw (2 stars, last pushed 4d ago), licensed MIT. It adds 125 tokens to every session and 1,087 once invoked, about $0.0006 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
react-best-practices
React development guidelines with hooks, component patterns, state management, and performance optimization.
vercel-deploy
Deploy applications to Vercel with edge functions, serverless, and ISR.
agents-md
Generate and safely maintain an AGENTS.md file (the cross-tool standard for guiding AI coding agents, backed by the Linux Foundation's Agentic AI Foundation and read natively by Codex, Cursor, Copilot, Gemini CLI, Aider, Windsurf, Zed, and more). Use this skill when the user wants to document a repo for AI agents…
skillcraft
Skill "skillcraft" from cloudroad-io/skillcraft, covering skillcraft, install, or: pip install skillcraft, commands and how it works.
implementation-loop
Disciplined plan-build-verify loop for implementing a feature or change. Use when building something new or modifying existing behavior, especially across multiple files.
debugging-loop
Systematic reproduce-isolate-fix-verify loop for bugs, test failures, and unexpected behavior. Use when something is broken and the cause is not yet known.