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/superclaude-org/superclaude_plugin/sc-researchgit clone --depth 1 https://github.com/SuperClaude-Org/SuperClaude_PluginWrote 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/superclaude-org/superclaude_plugin/sc-research)<a href="https://agentmods.dev/commands/superclaude-org/superclaude_plugin/sc-research"><img src="https://agentmods.dev/badge/commands/superclaude-org/superclaude_plugin/sc-research.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.00011 | $0.00836 |
| Opus 5 | $0.00005 | $0.00418 |
| Sonnet 5 | $0.00002 | $0.00167 |
| Haiku 4.5 | $0.00001 | $0.00084 |
Grade A, and why
research 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 — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/sc:sc:sc:research - Deep Research Command
Context Framework Note: This command activates comprehensive research capabilities with adaptive planning, multi-hop reasoning, and evidence-based synthesis.
Triggers
- Research questions beyond knowledge cutoff
- Complex research questions
- Current events and real-time information
- Academic or technical research requirements
- Market analysis and competitive intelligence
Context Trigger Pattern
/sc:sc:research "[query]" [--depth quick|standard|deep|exhaustive] [--strategy planning|intent|unified]
Behavioral Flow
1. Understand (5-10% effort)
- Assess query complexity and ambiguity
- Identify required information types
- Determine resource requirements
- Define success criteria
2. Plan (10-15% effort)
- Select planning strategy based on complexity
- Identify parallelization opportunities
- Generate research question decomposition
- Create investigation milestones
3. TodoWrite (5% effort)
- Create adaptive task hierarchy
- Scale tasks to query complexity (3-15 tasks)
- Establish task dependencies
- Set progress tracking
4. Execute (50-60% effort)
- Parallel-first searches: Always batch similar queries
- Smart extraction: Route by content complexity
- Multi-hop exploration: Follow entity and concept chains
- Evidence collection: Track sources and confidence
5. Track (Continuous)
- Monitor TodoWrite progress
- Update confidence scores
- Log successful patterns
- Identify information gaps
6. Validate (10-15% effort)
- Verify evidence chains
- Check source credibility
- Resolve contradictions
- Ensure completeness
Key Patterns
Parallel Execution
- Batch all independent searches
- Run concurrent extractions
- Only sequential for dependencies
Evidence Management
- Track search results
- Provide clear citations when available
- Note uncertainties explicitly
Adaptive Depth
- Quick: Basic search, 1 hop, summary output
- Standard: Extended search, 2-3 hops, structured report
- Deep: Comprehensive search, 3-4 hops, detailed analysis
- Exhaustive: Maximum depth, 5 hops, complete investigation
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 · 123 lines · 11 tokens per session scan A bae0ae6de23f
research is a command published in the GitHub repository SuperClaude-Org/SuperClaude_Plugin (55 stars, last pushed 15d ago), licensed MIT. It adds 11 tokens to every session and 836 once invoked, about $0.0001 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
research
Deep web research with adaptive planning and intelligent search.
create-namespace
Slash command that creates a new namespace file under system/namespaces/ in the personal repo, with lifecyclestate: scratch.
cc-council
Comprehensive multi-agent council review with 6 protocols, 10 specialists, scoped scoring (per-scope thresholds and weights), state machine orchestration, auto-fix, and 50+ configuration flags.
research
Deep web research with adaptive planning and intelligent search.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.