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.
npx skills add ThreeMoonsLab/agents-shipgate --skill claude-code-skillgit clone --depth 1 https://github.com/ThreeMoonsLab/agents-shipgateWrote 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/skills/threemoonslab/agents-shipgate/claude-code-skill)<a href="https://agentmods.dev/skills/threemoonslab/agents-shipgate/claude-code-skill"><img src="https://agentmods.dev/badge/skills/threemoonslab/agents-shipgate/claude-code-skill/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/skills/threemoonslab/agents-shipgate/claude-code-skill"><img src="https://agentmods.dev/badge/skills/threemoonslab/agents-shipgate/claude-code-skill.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00212 | $0.04646 |
| Opus 5.5 | $0.00085 | $0.01858 |
| Sonnet 5.5 | $0.00042 | $0.00929 |
| Haiku 4.5 | $0.00021 | $0.00465 |
Grade A, and why
agents-shipgate 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.
How it starts
The opening of the file, as written. The whole thing — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.
agents-shipgate skill
agents-shipgate is the deterministic merge gate for AI-generated agent capability changes — a local-first, static Tool-Use Readiness review. It analyzes shipgate.yaml plus tool sources (MCP exports, OpenAPI specs, OpenAI Agents SDK Python files, Anthropic Messages API artifacts, Google ADK files, LangChain/LangGraph files, CrewAI files, OpenAI API artifacts, Codex repo config, Codex plugin packages and marketplaces, n8n workflow JSON, Conductor OSS workflow JSON) and emits deterministic verifier artifacts, findings, Markdown, JSON, and SARIF.
It does not run agents, call tools, invoke LLMs, connect to MCP servers, or send telemetry by default. Static analysis only; audited exceptions are pinned in tests/test_adapter_static_only.py::ALLOWED_EXCEPTIONS.
The skill name is intentionally
agents-shipgate(notshipgate) so it does not collide with the/shipgateslash command shipped at.claude/commands/shipgate.md— Claude Code lets a skill with the same name preempt a command, which would bypass the bootstrap flow the slash command is meant to deliver.
When to use this skill
- The current diff adds or modifies MCP server or tool definitions,
@tool/@function_tooldecorators, OpenAPI specs describing agent tools, agent prompts, permission scopes, approval/confirmation policies, or agent CI workflows — run the verifier before reporting the change complete or creating a PR. - The user asks to add Tool-Use Readiness or pre-merge checks to an agent project.
- The user asks whether an AI-generated agent PR can merge.
- The repo already has
shipgate.yaml,agents-shipgate-reports/verifier.json, oragents-shipgate-reports/report.json. - The user asks to fix, triage, suppress, or explain a Shipgate finding.
- The user wants to add Shipgate to CI (GitHub Actions, GitLab CI, CircleCI).
When NOT to use this skill
- Generic linting / type checking — use the project's existing tooling.
- Runtime monitoring, evals, or behavioral testing — Shipgate is static-only.
- LLM output quality assessment — out of scope.
- Editing
agents-shipgate's own check implementations — that's upstream-repo work, not user-repo work.
What ships with it
11 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- .agents-shipgate-kit-metadata.json 11 KB
- ci-recipes/advisory-pr-comment.yml 1.1 KB
- prompts/add-shipgate-to-repo.md 16 KB
- prompts/decide-shipgate-relevance.md 10 KB
- prompts/explain-finding-to-user.md 6.5 KB
- prompts/fix-top-finding.md 9.3 KB
- prompts/recommend-fixes.md 8.0 KB
- prompts/stabilize-strict-mode.md 3.9 KB
- prompts/triage-false-positive.md 3.6 KB
- prompts/upgrade-shipgate-version.md 2.7 KB
- prompts/verify-agent-diff.md 4.5 KB
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 c474cec05fdb
- 1mo ago Changed b09ffc59ad9e
- 1mo ago First seen · 123 lines · 212 tokens per session scan A 6aedbd716d37
agents-shipgate is a skill published in the GitHub repository ThreeMoonsLab/agents-shipgate (90 stars, last pushed today), licensed Apache-2.0. It adds 212 tokens to every session and 4,646 once invoked, about $0.0008 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-08-30.
Other skills, from other repositories
github-workflow-automation
Advanced GitHub Actions workflow automation with AI swarm coordination, intelligent CI/CD pipelines, and comprehensive repository management.
ci-triage
Classify CI failures — distinguish clear regressions from infra flakes and security-test failures. Produces structured failure reports.
scanning-kubernetes-manifests-with-kubesec
Perform security risk analysis on Kubernetes resource manifests using Kubesec to identify misconfigurations, privilege escalation risks, and deviations from security best practices.
implementing-semgrep-for-custom-sast-rules
Write custom Semgrep SAST rules in YAML to detect application-specific vulnerabilities, enforce coding standards, and integrate into CI/CD pipelines.
securing-github-actions-workflows
This skill covers hardening GitHub Actions workflows against supply chain attacks, credential theft, and privilege escalation. It addresses pinning actions to SHA digests, minimizing GITHUBTOKEN permissions, protecting secrets from exfiltration, preventing script injection in workflow expressions, and implementing…
workflow-setup
Configures GitHub Actions CI/CD workflows for testing, linting, and deployment. Use when setting up automation for a Python, Rust, or TypeScript project.