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 ThreeMoonsLab/agents-shipgatenpx agentmods add plugins/threemoonslab/agents-shipgate/claude-codegit clone --depth 1 https://github.com/ThreeMoonsLab/agents-shipgateGrade A, and why
claude-code 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 yesterday.
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": "agents-shipgate",
"version": "0.16.0b7",
"description": "Run Agents Shipgate Tool-Use Readiness workflows from Claude Code. Skill-only: the plugin supplies the agents-shipgate skill and the /agents-shipgate:shipgate command; the scanner runs through the agents-shipgate CLI installed in the local environment (pipx install agents-shipgate, runtime contract 15). For the deterministic hooks (trigger check after edits, full verify at Stop), run: agents-shipgate install-hooks --target claude-code --write.",
"author": {
"name": "Three Moons Lab",
"email": "[email protected]",
"url": "https://threemoonslab.com/"
},
"homepage": "https://threemoonslab.com/",
"repository": "https://github.com/ThreeMoonsLab/agents-shipgate",
"license": "Apache-2.0",
"keywords": [
"agents",
"claude-code",
"tool-use-readiness",
"release-gate",
"mcp-security",
"policy-as-code"
]
}
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.
- yesterday First seen · 22 lines scan A b8b8b312bf42
claude-code is a plugin published in the GitHub repository ThreeMoonsLab/agents-shipgate (87 stars, last pushed 2d ago), licensed Apache-2.0. 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
mcp-bundle
Generate MCPB (MCP Bundle) packages for MCP server projects with manifest validation, bundle packaging, and CI/CD workflow integration.
codeeraser
Plugin marketplace listing 1 plugin: codeeraser.
ncoevoet-review-all
Marketplace for review-all — comprehensive, project-agnostic, multi-agent code review for Claude Code.
skillci
Lint, eval, and regression-test Claude Skills against a model matrix. Installs skillci-guardrails, which auto-verifies any SKILL.md an agent creates or edits with skillci check/eval before treating the change as done.
deploybot
DeployBot: a provider-neutral GitHub merge queue for coding agents.
craft
Full-stack developer toolkit with integrated workflow automation - 48 commands, 2 agents, 41 skills with standardized dry-run preview mode (29 with --dry-run support). Code, git, site, docs, testing, architecture, CI, distribution, teaching workflows, planning, release pipeline, and ADHD-friendly features including…