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 rules/superplanehq/superplane/integration-issue-conventionsgit clone --depth 1 https://github.com/superplanehq/superplaneWhat 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.00945 |
| Opus 5 | $0.00000 | $0.00473 |
| Sonnet 5 | $0.00000 | $0.00189 |
| Haiku 4.5 | $0.00000 | $0.00094 |
Grade A, and why
integration-issue-conventions 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.
How it starts
The opening of the file, as written. The whole thing — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SuperPlane Integration Issue Conventions
Apply these conventions whenever creating or editing integration base issues or component (trigger/action) issues for SuperPlane.
Template format: IMPORTANT block at top
Every issue body must start with the appropriate IMPORTANT block (then a blank line, then the rest of the content).
Base issues — use this block at the very top:
> 🚨 **IMPORTANT (critical)**
>
> This content has **not** passed detailed review yet.
> Review and rethink the suggested connection method before implementing.
> If unsure, reach out on **Discord** first.
Component issues (triggers and actions) — use this block at the very top:
> 🚨 **IMPORTANT (critical)**
>
> This content has **not** passed detailed review yet.
> Review and rethink configuration options and output channels before implementing.
> If unsure, reach out on **Discord** first.
For child issues, the parent reference line (**Parent (base integration):** #N) comes after this block, then the rest of the content.
Hierarchy and ordering
- Base issue first: One base integration issue per tool (e.g.
[GitHub] Base). All component issues (triggers and actions) are children of that base. - Child issues: One issue per component. Each child must include
**Parent (base integration):** #BASE_ISSUE_NUMBER(replace with the actual base issue number) immediately after the IMPORTANT block (see Template format above).
Title format
- Base:
[{Integration Name}] Base(e.g.[GitHub] Base,[ArgoCD] Base). - Actions:
[{Integration Name}] {Operation Name}in Title Case (e.g.[GitHub] Get Issue,[Slack] Archive Channel). - Triggers:
[{Integration Name}] On {Event}in Title Case (e.g.[GitHub] On Deployment,[GitHub] On Pull Request).
Configuration: Triggers vs Actions
- Actions (execute operations): Configuration fields must be execution parameters — what resource to operate on, how to perform the operation, what data to send. Not filters.
- Triggers (listen for events): Configuration fields must be filters — what events to listen for, what values to match (repository, status, labels). Not execution parameters.
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 · 74 lines · 0 tokens per session scan A 30c3ccd7b45f
integration-issue-conventions is a cursor rule published in the GitHub repository superplanehq/superplane (5,700 stars, last pushed today), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 945 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 cursor rules, from other repositories
project-overview
Overview of the Kaneo project structure, architecture, and key technologies.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.