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 agentmods add agents/threemoonslab/agents-shipgate/cursorgit clone --depth 1 https://github.com/ThreeMoonsLab/agents-shipgateWhat 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 | $0.00000 | $0.00427 |
| Opus 5 | $0.00000 | $0.00214 |
| Sonnet 5 | $0.00000 | $0.00085 |
| Haiku 4.5 | $0.00000 | $0.00043 |
Grade A, and why
cursor 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 2d 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
Use Agents Shipgate With Cursor
Cursor uses the shared agent-native protocol:
shipgate check --agent cursor --workspace . --format agent-boundary-json
Parse stdout as shipgate.agent_boundary_result/v2. Switch only on
control.state; follow control.next_action, control.allowed_next_commands,
and control.human_review. Treat decision as diagnostic context only.
--agent cursor labels the caller; it does not limit the check to Cursor files
or hide changes to another host's boundary.
If the binary is missing, surface the schema-valid install fixture with
control.state="agent_action_required", control.next_action.kind="install",
and command pipx install agents-shipgate.
After installation, rerun shipgate check; do not invent a natural-language
decision.
Cursor-specific discovery surfaces:
.cursor/cli.jsonShell/Read/Write permission rules.cursor/mcp.jsonMCP server declarations.cursor/rules/agents-shipgate.mdc- path globs for agent tools, policies, prompts, Codex plugin metadata, and CI release gates
Use shipgate audit --host --scope local-static to include supported
~/.cursor/cli-config.json and ~/.cursor/mcp.json declarations. UI choices,
session approvals, and invocation flags remain explicitly excluded.
For committed PR verification, use the CI substrate after the local check:
agents-shipgate verify --workspace . --config shipgate.yaml --base origin/main --head HEAD --ci-mode advisory --format json
Read agents-shipgate-reports/agent-handoff.json first, then
verifier.json, then verify-run.json, then report.json for reviewer
evidence. Legacy agent-result.json surfaces are supporting/provisional
compatibility projections for older automation consumers.
See protocol.md for the state machine, repair loop, policy discovery convention, and MCP read-only boundary.
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.
- 2d ago First seen · 46 lines · 0 tokens per session scan A fe2a12a56d22
cursor is an agent published in the GitHub repository ThreeMoonsLab/agents-shipgate (87 stars, last pushed 3d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 427 tokens. 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 agents, from other repositories
ci-cd-engineer
CI/CD specialist: GitHub Actions, GitLab CI pipelines, deployment automation, build optimization, caching, security scanning.
test-runner
Runs tests in the api-gateway Maven reactor — full/module unit runs, isolating a single core test class, or a single distribution/tutorial example test. Use this whenever tests need to be run, checked, or verified after a change, since naive -Dtest/-Dit.test invocations silently run (or skip) the wrong thing in this…
issue-feature-review
Review GitHub feature requests with constructive skepticism. Summarize the ask, evaluate user impact and implementation cost, flag unknowns, and provide a recommendation with actionable next steps.
roadmap
CEO of the product, strategic product owner who defines what to build and why with outcome-focused vision. Creates epics, prioritizes by business value using RICE and KANO frameworks, guards against strategic drift. Use when you need direction, outcomes over outputs, sequencing by dependencies, or user-value…
code-reviewer
You are a specialized code review subagent for Visor. Your role is to perform deep, comprehensive code reviews with a focus on.
toolsmith
Create OpenCode agents/commands/skills.