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/eveld/claude/researchgit clone --depth 1 https://github.com/eveld/claudeWhat 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.00458 |
| Opus 5 | $0.00000 | $0.00229 |
| Sonnet 5 | $0.00000 | $0.00092 |
| Haiku 4.5 | $0.00000 | $0.00046 |
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 2d 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 — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Research Codebase
You are conducting comprehensive codebase research by composing specialized skills.
Initial Response
When this command is invoked, respond with:
I'm ready to research the codebase. Please provide your research question or area of interest, and I'll analyze it thoroughly using specialized agents.
Then wait for the user's research query.
Workflow
Step 1: Read Mentioned Files
- If user mentions specific files (tickets, docs, JSON), read them FULLY first
- Use Read tool WITHOUT limit/offset parameters
- Read in main context before spawning sub-tasks
Step 2: Plan Research
- Analyze and decompose the research question
- Create research plan using TodoWrite
- Identify specific components and patterns to investigate
Step 3: Spawn Research Agents
- Use the
spawn-research-agentsskill to orchestrate parallel investigation - Follow the skill's guidance for agent selection and parallel execution
Step 4: Synthesize Findings
- Wait for ALL sub-agents to complete
- Compile results with specific file:line references
- Connect findings across components
- Answer user's specific questions with evidence
Step 5: Gather Metadata
- Use the
gather-project-metadataskill to collect git info, timestamps
Step 6: Write Document
- Use
determine-feature-slugskill to get feature slug (includes personal namespace) - Use the
write-research-docskill to create properly structured document - File path:
thoughts/{namespace}/NNNN-description/research.md(personal workspace) - Use
share-docsskill later to promote tothoughts/shared/for team collaboration - Old structure
thoughts/shared/research/YYYY-MM-DD-NN-description.mdstill supported for reading
Step 7: Present Results
- Show document path
- Summarize key findings
- Ask if user needs follow-up research
Important Notes
- NEVER run grep/glob directly - use agents via skills
- ALWAYS read mentioned files fully before spawning agents
- WAIT for all agents to complete before synthesizing
- Include file:line references in all findings
- Use TodoWrite to track research progress
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.
- 2d ago First seen · 58 lines · 0 tokens per session scan A 3de446ab4231
research is a command published in the GitHub repository eveld/claude (10 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 458 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-31.
Other commands, from other repositories
design-review
Workflow recipe — review a design end-to-end, ending in measured numbers rather than adjectives, by chaining 4 skills.
setup-pm-skills
Onboard a new user — find out what they do, recommend the right bundles & top skills, and set up a project CONTEXT.md so every skill is tailored to them.
statusbar-style
Switch the status-bar style (classic / capsule / hairline).
validate-dependencies
Validate all task dependencies for issues.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
config
Command "config" from sdebruyn/fabric-dw-mcp-cli, covering configuration & defaults, http retry budget, sql retry budget, mcp workspace allowlist {#mcp-workspace-allowlist} and mcp server log level.