integration-issue-conventions

integration-issue-conventions is a cursor rule for Cursor from superplanehq/superplane. It costs 0 tokens per session (945 once invoked), scanned A, original, no licence file.

A set of formatting rules for creating or editing SuperPlane integration issues. An integration connects SuperPlane to another tool, while base issues describe the connection and child issues describe individual triggers or actions.

In plain words
What is it for?
Use it when writing or editing SuperPlane integration, trigger, or action issues, especially in the integration project-management workflow or its temporary working directory.
Why use it?
It keeps issue content consistent and puts the required review warning in the correct place. It also preserves the parent-child relationship between a base integration issue and its components.

Cursor rule for Cursor

Written for Cursor: installed under .cursor/.

Good fit Use it when writing or editing SuperPlane integration, trigger, or action issues, especially in the integration project-management workflow or its temporary working directory.

Compare 6 cursor rules from other repositories ↓
Install with agentmods
npx agentmods add rules/superplanehq/superplane/integration-issue-conventions
About the project

SuperPlane is an open-source automation system that turns selected software backlog issues into pull requests by coordinating coding agents, source control, testing, review, and approvals. Engineering teams use it to automate routine development work while keeping ambiguous decisions for humans, and the catalogue add-ons support its workflows.

superplanehq/superplane · 7,825 stars · on GitHub · superplane.com

Install

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.

Clone the repo
git clone --depth 1 https://github.com/superplanehq/superplane

Made for: Cursor.

Wrote 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.

agentmods badge for integration-issue-conventions

README.md
[![agentmods](https://agentmods.dev/badge/rules/superplanehq/superplane/integration-issue-conventions/github.svg)](https://agentmods.dev/rules/superplanehq/superplane/integration-issue-conventions)
Your own site
<a href="https://agentmods.dev/rules/superplanehq/superplane/integration-issue-conventions"><img src="https://agentmods.dev/badge/rules/superplanehq/superplane/integration-issue-conventions/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.

agentmods 80×15 button for integration-issue-conventions

Your own site · 80×15
<a href="https://agentmods.dev/rules/superplanehq/superplane/integration-issue-conventions"><img src="https://agentmods.dev/badge/rules/superplanehq/superplane/integration-issue-conventions.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 945 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.00945
Opus 5.5 $0.00000 $0.00378
Sonnet 5.5 $0.00000 $0.00189
Haiku 4.5 $0.00000 $0.00094

Measured 1mo ago against content hash 30c3ccd7b45f, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 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.

.cursor/rules/integration-issue-conventions.mdc · 74 lines

The source is not reproduced here

A licence we could not identify

The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.

Read it on GitHub

Changes

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.

  1. 1mo ago First seen · 74 lines · 0 tokens per session scan A 30c3ccd7b45f

Subscribe to this mod's changes

integration-issue-conventions is a cursor rule published in the GitHub repository superplanehq/superplane (7,825 stars, last pushed today), with no licence file. 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.