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.
/plugin marketplace add mirkobozzetto/arsenalnpx agentmods add plugins/mirkobozzetto/arsenal/shipgit clone --depth 1 https://github.com/mirkobozzetto/arsenalWrote 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/plugins/mirkobozzetto/arsenal/ship)<a href="https://agentmods.dev/plugins/mirkobozzetto/arsenal/ship"><img src="https://agentmods.dev/badge/plugins/mirkobozzetto/arsenal/ship.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
ship 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 4d 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
{
"name": "ship",
"version": "1.10.0",
"description": "Spec executor. Implements a finalized brief or an Accepted propose (or a bare prompt via an inline contract) on agent-teams / subagents / solo, then emits a user-run verification bundle + a trace ledger.",
"author": {
"name": "Mirko Bozzetto",
"url": "https://github.com/mirkobozzetto"
},
"license": "MIT",
"homepage": "https://github.com/mirkobozzetto/arsenal/tree/main/plugins/ship"
}
What it installs
The manifest is a name and a version. 1 skill travel with it, and installing the plugin installs all of them — 181 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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.
- 4d ago First seen · 12 lines scan A 1e4ea6c109cf
ship is a plugin published in the GitHub repository mirkobozzetto/arsenal (15 stars, last pushed 4d ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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-30.
Other plugins, from other repositories
agent-teams
Orchestrate multi-agent teams for parallel code review, hypothesis-driven debugging, and coordinated feature development using Claude Code's Agent Teams.
kage
Kage manages your memory and agents. It briefs and runs agents in isolated git worktrees for a single run or a multi-wave goal, re-runs the checks itself instead of trusting the agent's report, and remembers what it learns so each brief is smarter than the last.
collate
历史论文 OCR 校对工作流：PDF 预处理去水印去角标、MinerU OCR、三类文献（繁体古籍 / 民国排印 / 现代简体）校对、公众号排版导出.
mosaic-bridge
Mosaic Bridge — Unity MCP assistant agents for scene building, shader creation, and session continuity.
before-you-build
Pre-build product risk review for founders, product teams, and AI-assisted builders before implementation starts.
standup
Summarize what you personally shipped over a time window from git history — an engineer standup or weekly recap, not a customer changelog. Scopes commits to your git author identity, reads the diffs, and classifies each as a feature, fix, refactor, tech-debt, or docs change. Use when the user asks what did I get done.