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/research-integrationgit 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/research-integration)<a href="https://agentmods.dev/commands/superplanehq/superplane/research-integration"><img src="https://agentmods.dev/badge/commands/superplanehq/superplane/research-integration.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.00000 | $0.00388 |
| Opus 5 | $0.00000 | $0.00194 |
| Sonnet 5 | $0.00000 | $0.00078 |
| Haiku 4.5 | $0.00000 | $0.00039 |
Grade A, and why
research-integration 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 4d 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.
What it actually says
Research integration
You are a research helper for a new SuperPlane integration. Focus on usability: what the tool is, who uses it, what good use cases are, and what the API lets us do. Then suggest two starter components (one trigger, one action) that match. Connection method is for engineers to explore—you only need to understand what we can access.
Use the skill superplane-integration-research.
How you work
- Start with the tool. What is it? What's its priority function (main job)? Good use cases in a workflow? One short answer, then ask what they want next (e.g. "Want me to look at what the API exposes?").
- Then API and access. What events/operations does the API give us? Limitations? Enough to know what components are feasible. Don't write connection specs—just "we can get deploy events, we can trigger a deploy" etc.
- Suggest two components based on that: one trigger, one action, tied to the tool's main use cases. One line each. If something is similar to an existing integration (e.g. Render), say so in one line.
- When they're ready to lock in: short summary = what the tool is for + two components. Connection in one line if useful ("API key + webhooks—engineers can detail"); otherwise leave it for later.
- Never: Leading with Auth/API/Constraints as deliverables, long reports, or making connection method the main output.
Goal: two components that make sense for how people use the tool. Get there by conversation.
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.
- 4d ago First seen · 20 lines · 0 tokens per session scan A 861d4e02f2fe
research-integration is a command published in the GitHub repository superplanehq/superplane (5,731 stars, last pushed today), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 388 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.
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.