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 agents/dmytri/shipshape/qmgit clone --depth 1 https://github.com/dmytri/shipshapeWhat 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.00030 | $0.00132 |
| Opus 5 | $0.00015 | $0.00066 |
| Sonnet 5 | $0.00006 | $0.00026 |
| Haiku 4.5 | $0.00003 | $0.00013 |
Grade A, and why
qm 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.
What it actually says
This agent mechanizes the Context bulkhead Article and the role transition rules. Doctrine lives in the skills; this file adds none.
You are the Shipshape Quartermaster. Load the shipshape:qm skill provided by this plugin and obey it exactly, including the shared shipshape skill Articles it requires. Your isolated context is the bulkhead: derive everything from durable repository artifacts and verification output you run. Deliver the skill's final report as your return value.
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 · 9 lines · 30 tokens per session scan A 10c796566736
qm is an agent published in the GitHub repository dmytri/shipshape (7 stars, last pushed 28d ago), licensed 0BSD. It adds 30 tokens to every session and 132 once invoked, about $0.0002 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 agents, from other repositories
design-interaction
Interaction Designer on the Atlas bench. Distinguishes click, hover, focus, selection, drag, keyboard, path, modal, and reversible states.
dvalin-security
After changing code that handles input, authentication, authorization, secrets, queries, commands, templates, dependencies, or deployment configuration.
resume
Agent "resume" from thixpin/pitway, covering resume, not a first-run command and recovery, including mid-flight quick-change.
code-reviewer
Code review, documentation quality, security audit, and quality assurance specialist with structured reasoning and semantic code analysis.
quant-backtest-validator
Validates backtesting execution realism, transaction costs, and market microstructure modeling.
qa-tester
Use this agent when you need to create comprehensive test specifications from user stories or requirements. This includes analyzing user stories to extract testable scenarios, developing detailed test cases with clear steps and expected outcomes, and creating structured test specification files that follow testing…