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.
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 skills/superplanehq/superplane/commit-and-pr-messagesnpx skills add superplanehq/superplane --skill commit-and-pr-messagesgit 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/commit-and-pr-messages)<a href="https://agentmods.dev/skills/superplanehq/superplane/commit-and-pr-messages"><img src="https://agentmods.dev/badge/skills/superplanehq/superplane/commit-and-pr-messages.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.00097 | $0.01338 |
| Opus 5 | $0.00048 | $0.00669 |
| Sonnet 5 | $0.00019 | $0.00268 |
| Haiku 4.5 | $0.00010 | $0.00134 |
Grade A, and why
commit-and-pr-messages 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 5d 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 — 143 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Commit and PR Messages
Write history that future readers can scan, search, and trust. A diff shows what changed; the message must explain why.
Based on How to Write a Git Commit Message (Chris Beams) and A Note About Git Commit Messages (Tim Pope), adapted for SuperPlane's Conventional Commits + DCO requirements.
Language: Write commit bodies, PR titles (after the type prefix), and PR descriptions in ASD-STE100 Simplified Technical English style. Follow simplified-technical-english before you finalize wording.
When to use
- Creating or amending a commit message
- Opening or updating a pull request (title and body)
- Reviewing whether a PR description is useful to reviewers
Commit messages — seven rules
- Separate subject from body with a blank line.
- Limit the subject line to ~50 characters (72 hard max). Prefer the
Conventional Commits prefix used by this repo (
feat:,fix:,chore:,docs:) plus a short imperative summary; keep the whole subject readable. - Capitalize the subject line after the optional type prefix
(
feat: Add canvas console filters). - Do not end the subject line with a period.
- Use the imperative mood in the subject line — as if completing:
If applied, this commit will ________.
Prefer
Fix,Add,Remove,RefactoroverFixed,Adds,Fixing. - Wrap the body at 72 characters.
- Use the body to explain what and why, not how. The code shows how. Cover motivation, prior behavior, trade-offs, and non-obvious side effects.
Model commit
Capitalized, short (50 chars or less) summary
More detailed explanatory text, if necessary. Wrap it to about 72
characters or so. The blank line after the subject is mandatory when a
body is present.
Explain the problem this commit solves and why this approach was chosen.
Leave mechanical how-details to the diff unless the approach is surprising.
Further paragraphs come after blank lines.
- Bullet points are okay
Resolves: #123
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.
- 5d ago First seen · 143 lines · 97 tokens per session scan A d0cdff531265
commit-and-pr-messages is a skill published in the GitHub repository superplanehq/superplane (5,731 stars, last pushed yesterday), licensed Apache-2.0. It adds 97 tokens to every session and 1,338 once invoked, about $0.0005 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
database-schema-designer
Design robust, scalable database schemas for SQL and NoSQL databases. Provides normalization guidelines, indexing strategies, migration patterns, constraint design, and performance optimization. Ensures data integrity, query performance, and maintainable data models.
iterate-pr
Iterate on a PR until CI passes. Optionally merge or merge and publish a release of the repo. Automates the feedback-fix-push-wait cycle.
qa-test-planner
Generate comprehensive test plans, manual test cases, regression test suites, and bug reports for QA engineers. Includes Figma MCP integration for design validation.
gen-relationship
Create and refine schema-backed Meshery relationship definitions (models//relationships/.json). Use for "add a relationship", "fix this relationship JSON", classifying kind/type/subType, or reviewing selectors and mutatorRef/mutatedRef patches between model components.
gepetto
Creates detailed, sectionized implementation plans through research, stakeholder interviews, and multi-LLM review. Use when planning features that need thorough pre-implementation analysis.
agent-md-refactor
Refactor bloated AGENTS.md, CLAUDE.md, or similar agent instruction files to follow progressive disclosure principles. Splits monolithic files into organized, linked documentation.