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.
Borrowing it
Nothing to install: this file belongs to superplanehq/superplane. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/superplanehq/superplane/main/.cursor/skills/superplane-issue-logger/SKILL.mdgit 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/skills/superplanehq/superplane/superplane-issue-logger)<a href="https://agentmods.dev/skills/superplanehq/superplane/superplane-issue-logger"><img src="https://agentmods.dev/badge/skills/superplanehq/superplane/superplane-issue-logger.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.1 | $0.00054 | $0.01625 |
| Opus 5 | $0.00027 | $0.00813 |
| Sonnet 5 | $0.00011 | $0.00325 |
| Haiku 4.5 | $0.00005 | $0.00162 |
Grade A, and why
superplane-issue-logger 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 6d 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 — 126 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SuperPlane Issue Logger
Use this skill when a user describes an improvement, bug, or request in natural language. You will: (1) research and understand it in SuperPlane context, (2) classify issue type, (3) propose title and body in tmp/pm_logger, and (4) optionally create the issue on GitHub with correct labels.
Reference: docs/contributing/ (issue-tracking, quality, pull-requests, etc.), https://docs.superplane.com/ when relevant.
1. Research and understanding
- Context: Use docs/contributing/ (issue-tracking, quality, pull-requests, integrations, component-design) and, when relevant, https://docs.superplane.com/ (product behavior, UX).
- Clarification: If the description is vague (e.g. "improve the canvas" or "fix the button"), prompt the user for: what exactly is wrong or desired, where in the app it happens, expected vs actual behavior, and (for bugs) steps to reproduce.
- Scope: One issue per draft. If the user describes multiple items, ask which one to capture first or create separate drafts.
2. Issue type classification
Map the user's description to exactly one of:
| Type | Definition |
|---|---|
| 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: If it breaks a flow or blocks usage → bug. If it's annoying or inconsistent but workable → papercut.
- Enhancement vs feature: Improves something that already exists → enhancement. Adds net-new capability → feature.
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.
- 6d ago First seen · 126 lines · 54 tokens per session scan A 3635ebf6cd21
superplane-issue-logger is a skill published in the GitHub repository superplanehq/superplane (5,803 stars, last pushed today), licensed Apache-2.0. It adds 54 tokens to every session and 1,625 once invoked, about $0.0003 per session on Opus 5. 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 skills, from other repositories
olares-doctor
Runtime diagnosis for Olares apps and the system via olares-cli — find the root cause when an app won't install or start, crashes, cannot pull an image, is running but unreachable, or is slow; includes doctor images and thirdleveldomain. Use for diagnosing catalog and dev app failures, not for authoring or editing…
k8s-control-plane
Control Plane Failure：API entities/etcd.md/Scheduler 问题的诊断与修复 Skill。.
troubleshoot-sandbox
Troubleshoot OpenSandbox issues by running diagnostics (logs, inspect, events, summary) via CLI or HTTP API to diagnose sandbox failures like OOM, crash, image pull errors, network problems, etc.
routing-calibration-loop
Calibrates routing changes against a live router endpoint with executable probes, local DSL validation, versioned deploys, and structured failure review. Use when tuning signals, projections, decisions, or maintained route examples against a real apiserver.
debugging-executions
Debug failed or wrong-output workflow executions using executions tools. Load when the user reports execution failures, unexpected node output, empty parameter values after a successful run, or a node showing a red or failed expression error.
n8n-docs-assistant
Answers n8n product, setup, credential, node, hosting, API, and usage questions from current n8n docs. Load n8n-docs via loadtool before calling it (search "n8n docs" if not visible). Use when the user asks how to configure, set up, troubleshoot, or understand n8n behavior, especially credential setup questions opened…