Borrowing it
Nothing to install: this file belongs to jnarowski/agentcmd. 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/jnarowski/agentcmd/main/.claude/commands/generate-research.mdgit clone --depth 1 https://github.com/jnarowski/agentcmdWrote 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/jnarowski/agentcmd/generate-research)<a href="https://agentmods.dev/commands/jnarowski/agentcmd/generate-research"><img src="https://agentmods.dev/badge/commands/jnarowski/agentcmd/generate-research/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/commands/jnarowski/agentcmd/generate-research"><img src="https://agentmods.dev/badge/commands/jnarowski/agentcmd/generate-research.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00011 | $0.01314 |
| Opus 5.5 | $0.00004 | $0.00526 |
| Sonnet 5.5 | $0.00002 | $0.00263 |
| Haiku 4.5 | $0.00001 | $0.00131 |
Grade A, and why
generate-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 2mo 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 — 211 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Parallel Research
You are a research orchestrator that deploys multiple subagents to investigate topics from different angles simultaneously. Read the Instructions and follow the Workflow below
Variables
- $featureName: $1 (optional)
- $researchTopic: $2
- $format: $3 (optional) - Output format: "text" or "json" (defaults to "text" if not provided)
Instructions
- Normalize $featureName (lowercase, hyphenated) for the output path
- If $researchTopic is not provided, stop IMMEDIATELY and ask the user to specify the topic.
- If $format is not provided, default to "text"
Workflow
When I give you a research question, you will:
- Deploy 4-5 parallel subagents using Task tool, each with a different research strategy
- Wait for all agents to complete
- Synthesize findings into a unified research document using exact structure from Synthesis Template
- Write this research doc to
.agent/specs/${featureName}-research.md
Subagent Templates
Agent 1: Broad Context
Task: Research "[TOPIC]" - Broad Context
- Search for overview, landscape, and general information
- Find 5-7 diverse sources covering different aspects
- Identify key concepts and terminology
- Note main players, tools, or solutions in this space
- Summarize in 500 words with source links
Agent 2: Deep Technical
Task: Research "[TOPIC]" - Technical Deep Dive
- Search for implementation details and technical specifications
- Find code examples, architecture patterns, and best practices
- Look for performance benchmarks and technical tradeoffs
- Identify common pitfalls and solutions
- Summarize in 500 words with source links
Agent 3: Problems & Alternatives
Task: Research "[TOPIC]" - Critical Analysis
- Search for problems, issues, and criticisms
- Find alternative approaches and competing solutions
- Look for failure cases and lessons learned
- Identify when NOT to use this approach
- Summarize in 500 words with source links
Agent 4: Real-World Usage
Task: Research "[TOPIC]" - Practical Applications
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.
- 2mo ago First seen · 211 lines · 11 tokens per session scan A e20f191e6a2f
generate-research is a command published in the GitHub repository jnarowski/agentcmd (18 stars, last pushed 10mo ago), licensed MIT. It adds 11 tokens to every session and 1,314 once invoked, about $0.0000 per session on Opus 5.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-09-01.
generate-research compared with commands from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| generate-researchjnarowski/agentcmd | Command | 18 | 10mo ago | MIT | A | 11 | Claude Code |
| checklistgithub/spec-kit | Command | 148k | yesterday | MIT | A | 13 | Claude Code |
| clarifygithub/spec-kit | Command | 148k | yesterday | MIT | A | 27 | Claude Code |
| specifygithub/spec-kit | Command | 148k | yesterday | MIT | A | 13 | Claude Code |
| analyzegithub/spec-kit | Command | 148k | yesterday | MIT | A | 26 | Claude Code |
| convergegithub/spec-kit | Command | 148k | yesterday | MIT | A | 35 | Claude Code |
| implementgithub/spec-kit | Command | 148k | yesterday | MIT | A | 14 | Claude Code |