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/issue-logger-conventionsgit clone --depth 1 https://github.com/superplanehq/superplaneWrote 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/rules/superplanehq/superplane/issue-logger-conventions)<a href="https://agentmods.dev/rules/superplanehq/superplane/issue-logger-conventions"><img src="https://agentmods.dev/badge/rules/superplanehq/superplane/issue-logger-conventions.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.00471 |
| Opus 5 | $0.00000 | $0.00235 |
| Sonnet 5 | $0.00000 | $0.00094 |
| Haiku 4.5 | $0.00000 | $0.00047 |
Grade A, and why
issue-logger-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 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.
What it actually says
SuperPlane Issue Logger Conventions
Apply these conventions when creating or editing issue drafts in tmp/pm_logger for general SuperPlane issues (non-integration).
Issue types
- bug: Something isn't working as expected (incorrect behavior, failure, regression).
- enhancement: Small/medium improvement to an existing feature already in the app.
- feature: Completely new feature or functionality.
- papercut: Small issue, bug, or inconsistency; minor improvement that doesn't break flows.
Bug vs papercut: breaks a flow or blocks usage → bug. Annoying but workable → papercut.
Title and body
- Title: Short — max 40 characters. One or two concrete concepts; not a full list of details, not too vague. Stored in the file as
### Title(or clear header) so the log-to-GitHub step can reuse it. - Body: Use the per-type template from the issue-logger skill (bug, papercut, enhancement, feature). Keep drafts short and efficient; no empty sections. Do not put Priority in the body — Priority is set only via the Board Project field when logging to GitHub.
- Priority: Always suggested (P1–P4) and confirmed with the user before writing the draft and before logging to GitHub; store only in memory or Board, never in the draft body.
When creating issues on GitHub
- Never log the issue until the user has verified the draft (title, body, type, priority) and explicitly approved (e.g. "looks good", "log it").
- Create issues sequentially to avoid API rate limiting.
- Use one type label per issue:
bug,enhancement,feature, orpapercut(match repo labels). - Add to SuperPlane Board (project 2) and set Priority via Board fields. Do not set Integration Status for general issues.
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 · 34 lines · 0 tokens per session scan A f76a398dae87
issue-logger-conventions is a cursor rule published in the GitHub repository superplanehq/superplane (5,700 stars, last pushed yesterday), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 471 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
development-conventions
Development conventions, code style, and best practices for the Kaneo project.
backend
You are an expert in Go, Gin, Gorm, Gen, Cosy (https://cosy.uozi.org/) with a deep understanding of best practices and performance optimization techniques in these technologies.
gsd-ship-labels
After /gsd-ship creates a PR, always run gsd-ship-post (labels + optional changeset).
backend-python
Cursor rule "backend-python" from coeusyk/inference-x, covering backend python rules, stack assumptions, code style, fastapi conventions and schema conventions.
restart
When restarting anything.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.