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/felipearomani/claude-shipyardWrote 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/felipearomani/claude-shipyard/fleet)<a href="https://agentmods.dev/plugins/felipearomani/claude-shipyard/fleet"><img src="https://agentmods.dev/badge/plugins/felipearomani/claude-shipyard/fleet/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/plugins/felipearomani/claude-shipyard/fleet"><img src="https://agentmods.dev/badge/plugins/felipearomani/claude-shipyard/fleet.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
fleet 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 1mo 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": "fleet",
"version": "0.3.0",
"description": "Plan, dispatch and land work across a fleet of autonomous Claude Code agents.",
"author": {
"name": "Felipe Romani",
"url": "https://github.com/felipearomani"
},
"homepage": "https://github.com/felipearomani/claude-shipyard",
"repository": "https://github.com/felipearomani/claude-shipyard",
"license": "MIT",
"keywords": [
"multi-agent",
"orchestration",
"planning",
"autonomous-agents",
"code-review",
"fleet"
]
}
What it installs
The manifest is a name and a version. 4 skills, 3 agents travel with it, and installing the plugin installs all of them — 1,359 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.
- 1mo ago Changed 0d636cbf306a
- 1mo ago First seen · 21 lines scan A aaa755006de1
fleet is a plugin published in the GitHub repository felipearomani/claude-shipyard (1 stars, last pushed 1mo 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-31.
Other plugins, from other repositories
orchestrate
Decompose a large goal into a tree of parallel workers running in isolated git worktrees, collect typed handoffs, replan, repeat until terminal. Idiomatic Claude Code realization of Cursor /orchestrate.
ci-review
CI-optimized code review: multi-agent parallel review with confidence scoring and atomic GitHub PR review posting via gh api.
secondmate
Your agent writes the code, a different model tries to break it, and only what survives ships. Cross-model, edit-locked review with a machine-readable verdict, gated merges, durable decisions, stuck-loop and timeout guards, and read-only reasoning one-shots. Harness-neutral.
relay
Delegate work packets from a lead Claude Code session to executor sessions in their own iTerm tabs, with session reuse instead of always spawning fresh.
vibe-flow
Orchestration skills for Vibe Kanban: plan → ship → link → review → merge with wave-based dispatch, executor routing (T0-T4), and autonomous fix loops.
orodruin-labs marketplace
Plugin marketplace listing 1 plugin: nazgul.