research-extension

research-extension is a command for Cursor from superplanehq/superplane. It costs 0 tokens per session (304 once invoked), scanned A, original, Apache-2.0.

A conversational research helper for extending an existing SuperPlane integration, an integration that connects SuperPlane to another tool.

In plain words
What is it for?
Use it to identify missing use cases, check available API capabilities and limits, and suggest additional integration components.
Why use it?
It shows what the integration already covers, what users may still need, and what the connected tool's API makes possible.

Command for Cursor

About the project

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.

superplanehq/superplane · 5,731 stars · on GitHub

Install

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.

agentmods
npx agentmods add commands/superplanehq/superplane/research-extension
Clone the repo
git clone --depth 1 https://github.com/superplanehq/superplane

Made for: Cursor.

Wrote 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.

agentmods badge for research-extension

README.md
[![agentmods](https://agentmods.dev/badge/commands/superplanehq/superplane/research-extension.svg)](https://agentmods.dev/commands/superplanehq/superplane/research-extension)
Your own site
<a href="https://agentmods.dev/commands/superplanehq/superplane/research-extension"><img src="https://agentmods.dev/badge/commands/superplanehq/superplane/research-extension.svg" alt="Measured on agentmods" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 304 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.00304
Opus 5 $0.00000 $0.00152
Sonnet 5 $0.00000 $0.00061
Haiku 4.5 $0.00000 $0.00030

Measured 5d ago against content hash 1064cf04348a, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

research-extension 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.

.cursor/commands/research-extension.md · 20 lines

What it actually says

Research extension

You are a research helper for extending an existing SuperPlane integration. Focus on usability: what's the tool's priority function, what use cases we're not covering yet, what the API allows. Then suggest additional components that fit. Connection details stay with engineers—you only need to know what we can access.

Use the skill superplane-integration-research.

How you work

  1. Start with what we have. What's already in the integration (from docs/components/ or docs)? One short answer. Then: what's the tool's main job and use cases we might be missing?
  2. Then API. What else does the API expose that fits those use cases? Limitations? Enough to know what's feasible—no connection specs.
  3. Suggest a few more components that match priority function and use cases. One line each. Ask if they want to add or drop any.
  4. When they're ready to lock in: short summary = what's already there + additional components. Connection only if relevant in one line.
  5. Never: Leading with connection method, long reports, or engineering-focused output.

Goal: a small set of additional components that make sense for how people use the tool. Get there by conversation.

Changes

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.

  1. 5d ago First seen · 20 lines · 0 tokens per session scan A 1064cf04348a

Subscribe to this mod's changes

research-extension is a command published in the GitHub repository superplanehq/superplane (5,731 stars, last pushed yesterday), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 304 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.