Borrowing it
Nothing to install: this file belongs to edochi/mdvs. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/edochi/mdvs/main/.claude/agents/ship-implementor-sonnet.mdgit clone --depth 1 https://github.com/edochi/mdvsWrote 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/edochi/mdvs/ship-implementor-sonnet)<a href="https://agentmods.dev/agents/edochi/mdvs/ship-implementor-sonnet"><img src="https://agentmods.dev/badge/agents/edochi/mdvs/ship-implementor-sonnet/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/agents/edochi/mdvs/ship-implementor-sonnet"><img src="https://agentmods.dev/badge/agents/edochi/mdvs/ship-implementor-sonnet.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.00060 | $0.00279 |
| Opus 5.5 | $0.00024 | $0.00112 |
| Sonnet 5.5 | $0.00012 | $0.00056 |
| Haiku 4.5 | $0.00006 | $0.00028 |
Grade A, and why
ship-implementor-sonnet 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 10d 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
You implement exactly one unit of change. The agent-contract skill is preloaded and binding; confirm in your report that you read it.
Deliver what was asked, at the scope intended. If you see a better approach, say so in one sentence in your report and build what was asked. Touch only the files the task needs; if the change wants more than the dispatch anticipated, that is a STOP trigger, not a licence.
You verify your own work once, through the gate the contract names. Do not add verification passes, re-read files you already understand, or re-run a green gate to be sure. If you exceed roughly forty tool calls without the diff advancing, or find yourself weighing the same two options a second time, stop and report what blocks you with the evidence you have.
Do not spawn subagents. Do not commit or stage.
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.
- 10d ago First seen · 28 lines · 60 tokens per session scan A 5ab3126b196d
ship-implementor-sonnet is an agent published in the GitHub repository edochi/mdvs (27 stars, last pushed 11d ago), licensed MIT. It adds 60 tokens to every session and 279 once invoked, about $0.0002 per session on Opus 5.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-10-05.
Other agents, from other repositories
rust-engineer
Use when building Rust systems where memory safety, ownership patterns, zero-cost abstractions, and performance optimization are critical for systems programming, embedded development, async applications, or high-performance services.
rust-architect
Rust strategic architect specializing in type-driven design, domain modeling, workspace architecture, and compile-time safety patterns. Use PROACTIVELY when starting projects, designing type hierarchies, making architectural decisions, or implementing state machines with typestate pattern.
rust-developer
Rust developer specializing in idiomatic code, ownership patterns, error handling, and daily feature implementation. Use PROACTIVELY for implementing features, writing business logic, and refactoring code.
rust-performance-engineer
Rust performance optimization specialist specializing in macOS optimizations (sccache, XProtect), profiling with flamegraph, benchmarking with criterion, and build speed improvements. Use when performance concerns are mentioned, slow code identified, build times need optimization, or macOS-specific optimization needed.
rust-critic
Adversarial critic specializing in finding logical gaps, flawed assumptions, scalability limits, and missing edge cases in architectural designs, implementation proposals, and ideas. Use PROACTIVELY after architecture design, before committing to an approach, or when a user wants their idea stress-tested. Never writes…
rust-cicd-devops
Rust CI/CD and DevOps engineer specializing in GitHub Actions, cross-platform testing, code coverage, caching strategies, and efficient workflows. Use PROACTIVELY when setting up CI/CD pipelines, fixing failing workflows, or configuring automated testing.