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.
git clone --depth 1 https://github.com/JasonWarrenUK/goblin-modeWrote 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/agents/jasonwarrenuk/goblin-mode/ship-checker)<a href="https://agentmods.dev/agents/jasonwarrenuk/goblin-mode/ship-checker"><img src="https://agentmods.dev/badge/agents/jasonwarrenuk/goblin-mode/ship-checker.svg" alt="Measured on agentmods" 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.00077 | $0.01132 |
| Opus 5 | $0.00039 | $0.00566 |
| Sonnet 5 | $0.00015 | $0.00226 |
| Haiku 4.5 | $0.00008 | $0.00113 |
Grade A, and why
ship-checker 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 7d 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- 7d ago First seen · 136 lines · 77 tokens per session scan A 7ddedc9e8b56
ship-checker is an agent published in the GitHub repository JasonWarrenUK/goblin-mode (5 stars, last pushed 11d ago), with no licence file. It adds 77 tokens to every session and 1,132 once invoked, about $0.0004 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
commit-reviewer
Pre-commit review for staged changes. Checks for debug code, secrets, missing tests and unintended files. Use when: "review commit", "check staged", "pre-commit review", "what have I staged".
project-shipper
PROACTIVELY use this agent when approaching launch milestones, release deadlines, or go-to-market activities. This agent specializes in coordinating launches, managing release processes, and executing go-to-market strategies within the 6-day development cycle. Should be triggered automatically when release dates are…
herald
Release prep, version bumps, changelog generation.
code-reviewer
Code review specialist. Reviews code quality, security, performance, and test coverage. Automatically runs on "review code", "code review please" requests.
evolve-merge-to-main-gate
Merge-to-main promotion-readiness gate for the Evolve Loop (Evaluate archetype). The campaign executor invokes this at milestone/wave boundaries to verify a completed milestone's already-integrated work is ready to be promoted to main, emitting a PASS/WARN/FAIL verdict plus mergegate. signals. READ-ONLY — it never…
git-workflow-agent
Git workflow specialist who manages branching, committing, syncing, pull requests, releases, and hotfixes using conventional commits, branch naming standards, and code review guidelines.