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-askWrote 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-ask)<a href="https://agentmods.dev/skills/xydisorder/shipjaw/shipjaw-ask"><img src="https://agentmods.dev/badge/skills/xydisorder/shipjaw/shipjaw-ask/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-ask"><img src="https://agentmods.dev/badge/skills/xydisorder/shipjaw/shipjaw-ask.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.02965 |
| Opus 5.5 | $0.00000 | $0.01186 |
| Sonnet 5.5 | $0.00000 | $0.00593 |
| Haiku 4.5 | $0.00000 | $0.00297 |
Grade A, and why
shipjaw-ask 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 24d 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 — 207 lines — stays where its author put it; the contents beside it link to each section on GitHub.
shipjaw-ask
Continuation-only. Do not reload bootstrap discovery/architecture or
the full shipjaw-build SKILL body. Trust project tooling + docs.
Challenge plans/choices (built-in — not slash-only)
Agents must challenge non-trivial plans and choices in this session
(prefer a separate Task/subagent as Challenger). Do not wait for the
user to type /shipjaw-challenge.
Before coding a new phase, new auth/persistence, primary UI, money/
authz, or any ADR/stack fork not forced by tech-choices.md:
- Ensure the phase (or ADR) exists.
- Pick the tier first — full pass vs. light self-check, per
../shipjaw-build/references/challenge-built-in.md"Scale the pass to actual stakes" (full pass for auth/money/shared data/multi-user/ irreversible/contradicts an existing decision; light self-check for single-user, purely additive, reversible, presentation-only changes). Unsure which → full pass once. - Full pass: Proposer ≤8 bullets → Challenger attacks (5 axes: product / business / tech / pragmatism / design). Prefer subagent; else same-session hard role flip. ≥1 Change/Defer or “no alternative + why”. No rubber-stamp. Light self-check: one short paragraph — biggest real risk + how it's handled — no subagent, no axis table.
- Apply plan edits; note the pass (and tier) in the phase Challenge
section (
built-in <date>is enough unless escalating). - Only then implement.
Escalate to /shipjaw-challenge when the user asks, the plan stays
unstable, or you want a durable challenge-report.md. Detail:
../shipjaw-build/references/challenge-built-in.md (open only if unsure).
Skip only for tiny fixes inside an already-challenged phase (cite prior).
Binding defaults (do not open principles unless conflict)
- State lives in committed
documentation/— update before done. - Progressive disclosure — INDEX → handoff.md → ≤2 files; Grep + offset reads.
- Project owns conventions after bootstrap (tsconfig/eslint/CI/docs).
- Core User can… first; no Out-of-v1 / drive-by scope.
- Types / consts / helpers by ownership (
domain/application/features/<f>/lib) — no grab-baglib/utils.ts. - Ports in
application/ports/; wire incomposition.ts; actions stay thin (validate → use-case → map errors). - Bug ⇒ failing-then-passing regression test; never weaken tests to green.
- Gate once; stop after 2 failed fix attempts; ask the human.
- End every run by overwriting
documentation/handoff.md(template../shipjaw-build/templates/handoff.md) with next slash command. - On doc↔code drift, stop and resolve (see below) — don’t invent.
- Challenge non-trivial plans/choices in-session (prefer
Task/subagent);
/shipjaw-challengeonly for full report / escalate. - Stamp lag: if
scaffolded-with/adopted-withis behind the installedshipjaw-build/VERSION, tell the user once and prefer/shipjaw-upgradebefore heavy product work (unless they insist on the feature now). Run../shipjaw-build/scripts/changelog-since-stamp.sh <root>when explaining what changed. - Session-size budget (no agent can trigger
/compactitself — saying it early is the only lever): a request needing more than one phase is not one session — finish the current phase (gate + docs + handoff), then suggest/compact/fresh chat before starting the next phase, even if nothing failed. Chasing a non-gate bug past ~6 file reads without root cause → same reminder, before going deeper.
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.
- 24d ago Changed · +2 lines d521a7b40735
- 1mo ago Changed · +8 lines e36f4d3fa7f8
- 1mo ago Changed 174dd554364a
- 2mo ago First seen · 197 lines · 0 tokens per session scan A 899c4a33f085
shipjaw-ask is a skill published in the GitHub repository XyDisorder/shipjaw (2 stars, last pushed 25d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,965 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
planning-with-files
Persistent file-based planning for multi-step AI-agent work. Keeps taskplan.md, findings.md, and progress.md on disk; lifecycle hooks inject selected project planning context. Automatic recovery reads project planning files only. Explicit session-catchup.py --metadata reads same-project local agent session records and…
bopomofo-rescue
A text-recovery tool for Taiwanese Bopomofo, also called Zhuyin, keyboard mistakes. It converts letter-and-number sequences typed with the wrong input mode back into likely Chinese text.
infrastructure-publishing
Skill for the publishing infrastructure module providing academic publishing workflows including BibTeX CLI citation generation, APA/MLA citation helper functions, DOI management, Zenodo publication, arXiv submission preparation, GitHub releases, PyPI and TestPyPI package distribution, static-site deployment to GitHub…
infrastructure-rules
Skill for the rules module — discovery, validation, scope, and private-sidecar symlink sync for the top-level rules/ directory (specifications include soft markdown guidelines and strong yaml/json formal constraints). Use when discovering rules (discoverrules), resolving a rule path (resolveruleroot), validating rule…
infrastructure-tools
Skill for the tools module — discovery, validation, scope, and private-sidecar symlink sync for the top-level tools/ directory (executable entry points such as scripts, skills, and agents stored as passive manifests with scripts/ directories). Use when discovering tools (discovertools), resolving a tool path…
template-academic-paper
Template-native manuscript planning, outline, drafting, revision, formatting, citation check, and AI-use disclosure routing. USE WHEN the user asks to write, outline, revise, format, or prepare a paper inside the Research Project Template.