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 commands/superplanehq/superplane/changeloggit 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/commands/superplanehq/superplane/changelog)<a href="https://agentmods.dev/commands/superplanehq/superplane/changelog"><img src="https://agentmods.dev/badge/commands/superplanehq/superplane/changelog.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.00035 | $0.00611 |
| Opus 5 | $0.00017 | $0.00305 |
| Sonnet 5 | $0.00007 | $0.00122 |
| Haiku 4.5 | $0.00003 | $0.00061 |
Grade A, and why
changelog 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 — 27 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Changelog
Generate a changelog of what was merged to main for a given time range. The output is a single markdown file in tmp/ with new integrations, new components and triggers, improvements, security updates, and bug fixes.
Use the skill superplane-changelog for the full workflow: time range, classifying commits (new integrations vs new components vs improvements vs security vs bug fixes), format rules (no em dashes, no "We", Integration: components, user-focused improvements, dedicated Security section with CVE when available), and output structure. Section titles must include numeric counts for both integrations (e.g. "#### 3 new integrations") and components/triggers (e.g. "#### 12 new components and triggers").
Input
- Time range (required): e.g. "since Monday", "last 5 days", "since last Friday", "from Feb 3 to now", or "since v0.6.0". If the user does not specify, ask or default to "since Monday (5 days)".
Process
- Determine start and end of the window. When the range is version-based (e.g. "since v0.6.0"), use date and time: get the tag's commit timestamp (e.g.
git log -1 --format="%cI" v0.6.0) so the window is strictly after the tag and same-day commits before the tag are excluded. - Run
git log --since="<start>" --format="%h %ad %s" mainwith<start>as a date (YYYY-MM-DD) or as the tag's ISO 8601 timestamp when using a version tag. Use--date=shortor--date=isoas appropriate. Use the result to identify what landed in the window. - Classify: new integrations (whole integration new), new components/triggers only (filter by date; for existing integrations list only new components), user-facing improvements (no tech-only items), security fixes (separate section; CVE when available), bug fixes. Do not include or derive entries from
chore:commits. Omit bug/security fixes that only affect a component or integration introduced in this changelog window. - Resolve component/trigger names from
pkg/integrations/andpkg/components/(Labels). - Write
tmp/changelog_<start>_to_<end>.mdfollowing the skill's structure and format rules.
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 · 27 lines · 35 tokens per session scan A 17f312a3a776
changelog is a command published in the GitHub repository superplanehq/superplane (5,731 stars, last pushed yesterday), licensed Apache-2.0. It adds 35 tokens to every session and 611 once invoked, about $0.0002 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 commands, from other repositories
fix-pr-review-comments
Analyze PR comments, implement fixes, and post targeted responses.
OPSX: Sync
Sync delta specs from a change to main specs.
triage
Triage Linear issue with comprehensive analysis.
card
Open one self-contained OverClick card.
framework-builder
Run the real Limitless framework builder for a topic.
review-pr
Comprehensive PR review checklist to ensure code quality, testing, and best practices.