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/use-with-cursorgit 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/agents/threemoonslab/agents-shipgate/use-with-cursor)<a href="https://agentmods.dev/agents/threemoonslab/agents-shipgate/use-with-cursor"><img src="https://agentmods.dev/badge/agents/threemoonslab/agents-shipgate/use-with-cursor.svg" alt="Measured on agentmods" height="20"></a>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 | $0.00000 | $0.02167 |
| Opus 5 | $0.00000 | $0.01084 |
| Sonnet 5 | $0.00000 | $0.00433 |
| Haiku 4.5 | $0.00000 | $0.00217 |
Grade A, and why
use-with-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 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.
How it starts
The opening of the file, as written. The whole thing — 166 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Use Agents Shipgate with Cursor
This page is the compatibility guide for Cursor rules. For the normative agent protocol, use cursor.md and protocol.md. The canonical Cursor control command is:
shipgate check --agent cursor --workspace . --format agent-boundary-json
Parse stdout as shipgate.agent_boundary_result/v2, switch on
control.state, and follow control.next_action,
control.allowed_next_commands, and control.human_review. Treat decision
as diagnostic context only; do not infer local control from prose.
Cursor's discoverability surface is the auto-attach project rule: a Markdown file under .cursor/rules/*.mdc with frontmatter that lists which globs cause it to attach to a chat. The canonical Shipgate rule already exists as a copy-paste snippet — drop it in and Cursor will load it whenever a chat touches shipgate.yaml, an OpenAPI/MCP spec, a tools JSON, or any .py file.
| Surface | What it does | Source path in this repo |
|---|---|---|
.cursor/rules/agents-shipgate.mdc |
Auto-attaches to chats that touch agent-tool surfaces. Tells Cursor when and how to run Shipgate. | docs/target-repo-agent-snippets.md §.cursor/rules/agents-shipgate.mdc |
| Reusable prompts | Cursor reads pasted Markdown directly in chat / composer (Cmd+L). Copy the body of any prompts/*.md recipe. |
prompts/README.md |
Cursor's rule mechanism is analogous to Claude Code's skill auto-trigger, not to a slash command. It fires when the chat context matches the rule's globs — there is no manual invocation step.
Install Agents Shipgate
From the root of your agent project:
pipx install agents-shipgate
agents-shipgate self-check --json
See AGENTS.md §Install for fallbacks (pip, uv, python -m).
Drop in the Cursor rule
Open docs/target-repo-agent-snippets.md and copy the .cursor/rules/agents-shipgate.mdc snippet (the second-to-last fenced block, under §.cursor/rules/agents-shipgate.mdc) into your repo at exactly that path:
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 · 166 lines · 0 tokens per session scan A 1e1e167ac058
use-with-cursor is an agent published in the GitHub repository ThreeMoonsLab/agents-shipgate (87 stars, last pushed today), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 2,167 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.
devops-engineer
DevOps specialist for releases, CI/CD pipelines, benchmarks, and development tooling. Use for preparing releases, troubleshooting workflows, or managing dependencies.
devops_engineer
专业DevOps工程师，负责部署、基础设施和CI/CD流水线.
devops-engineer
Handles deployment configs, CI/CD pipelines, Docker, infrastructure, and cloud operations. Use for deployment reviews and infrastructure tasks.
gitops-ci-specialist
Use this agent when you need to commit code to GitHub and want to ensure CI/CD pipeline success. Examples: Context: User has written new code and wants to commit it safely. user: 'I've added a new authentication module. Can you help me commit this properly?' assistant: 'I'll use the gitops-ci-specialist agent to…
karimo-reviewer
Validates completed PRDs, checks task quality, generates dependency graphs, and catches issues before execution. Use after PRD interview completes.