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-dashboard-and-widgets/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-dashboard-and-widgets)<a href="https://agentmods.dev/skills/superplanehq/superplane/superplane-dashboard-and-widgets"><img src="https://agentmods.dev/badge/skills/superplanehq/superplane/superplane-dashboard-and-widgets/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.
<a href="https://agentmods.dev/skills/superplanehq/superplane/superplane-dashboard-and-widgets"><img src="https://agentmods.dev/badge/skills/superplanehq/superplane/superplane-dashboard-and-widgets.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00090 | $0.04039 |
| Opus 5 | $0.00045 | $0.02020 |
| Sonnet 5 | $0.00018 | $0.00808 |
| Haiku 4.5 | $0.00009 | $0.00404 |
Grade A, and why
superplane-dashboard-and-widgets 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 10d 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 — 250 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SuperPlane console and widgets
Use this skill when working on per-canvas consoles: the console mode overlay, typed panels, widget renderers, YAML import/export, or backend validation.
Canonical reference: docs/prd/console-and-widgets.md — read it for full schemas, examples, and maintenance notes. This skill is the operational subset for agents.
Product rules (do not break)
- One console per canvas (not templates). Stored as versioned JSON
panels+layouton the canvas version. - Console mode hides the graph; 12-column
react-grid-layout(ConsoleView). - Edit (panels, layout, YAML import):
canvases:update, not template, canvas not deleted. - Run (node panel Run, table / board row actions): same as edit —
InvokeNodeTriggerHook; UI usescanRunNodes. - YAML import is replace-all (max 50 panels, 1 MiB payload).
- User-facing name: SuperPlane (capital P).
- Row actions are
kind: triggeronly — they fire trigger nodes; they do not call HTTP Request nodes directly.
Layer map
| Layer | Key paths |
|---|---|
| Console page | web_src/src/pages/app/console/ConsoleView.tsx — grid, Add Panel picker, YAML modal wiring |
| Context | console/ConsoleContext.tsx, ConsoleContextProvider.tsx |
| Trigger hook | console/useConsoleRunTrigger.ts, useConsoleTriggerLock.ts |
| Panel router | console/ConsolePanelCards.tsx |
| Schema | console/panelTypes.ts — types, templates, validators, normalizeTablePanelContent, normalizeBoardPanelContent |
| YAML (FE) | console/consoleYaml.ts, ConsoleYamlModal.tsx |
| Widget data | console/widget/useWidgetData.ts |
| Widget UI | console/widget/WidgetTable.tsx, WidgetBoard.tsx, WidgetChart.tsx, WidgetNumber.tsx, WidgetScorecard.tsx |
| Backend | pkg/yaml/console.go — YAML import/export + validators |
| Proto | protos/canvases.proto — console panels live on the canvas version |
Invariant: panelTypes.ts validators (plus satellite modules like boardPanelContent.ts and nodesPanelContent.ts), pkg/yaml/console.go, and widget types.ts must agree. Frontend fast-fails; backend is authoritative on import.
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.
- 10d ago First seen · 250 lines · 90 tokens per session scan A 6f28f425149b
superplane-dashboard-and-widgets is a skill published in the GitHub repository superplanehq/superplane (6,405 stars, last pushed today), licensed Apache-2.0. It adds 90 tokens to every session and 4,039 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
performing-kubernetes-etcd-security-assessment
Assess the security posture of Kubernetes etcd clusters by evaluating encryption at rest, TLS configuration, access controls, backup encryption, and network isolation.
add-feature
Add a new UI feature to the nvcf-ui app — folder structure, routing, data loading, lazy-loading, testing, and completion checklist. Use when creating a new feature folder, adding a page or view, wiring routes, building a new screen, or deciding whether to extend an existing feature vs create a new one. Also use when…
testing
Writing frontend tests for the nvcf-ui app — Vitest, Testing Library, MSW, and project-specific render helpers. Use when creating test files, writing component tests, setting up MSW handlers in tests, deciding which render helper to use, or when the user is adding or modifying a UI component and hasn't mentioned tests…
run
Start the nvcf-ui development server. Use when asked to run, start, or launch the app, or to verify a change works in the browser.
vercel-react-best-practices
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance…
vercel-composition-patterns
React composition patterns that scale. Use when refactoring components with boolean prop proliferation, building flexible component libraries, or designing reusable APIs. Triggers on tasks involving compound components, render props, context providers, or component architecture. Includes React 19 API changes.