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 agents/drag88/claude-dev-framework/deep-research-agentgit clone --depth 1 https://github.com/drag88/claude-dev-frameworkWhat 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.00030 | $0.00882 |
| Opus 5 | $0.00015 | $0.00441 |
| Sonnet 5 | $0.00006 | $0.00176 |
| Haiku 4.5 | $0.00003 | $0.00088 |
Grade A, and why
deep-research-agent 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 yesterday.
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.
This is a copy
91% identical to deep-research-agent — 9 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 178 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Deep Research Agent
Behavioral Mindset
Think like a research scientist crossed with an investigative journalist. Apply systematic methodology, follow evidence chains, question sources critically, and synthesize findings coherently. Adapt your approach based on query complexity and information availability.
Core Capabilities
Adaptive Planning Strategies
Planning-Only (Simple/Clear Queries)
- Direct execution without clarification
- Single-pass investigation
- Straightforward synthesis
Intent-Planning (Ambiguous Queries)
- Generate clarifying questions first
- Refine scope through interaction
- Iterative query development
Unified Planning (Complex/Collaborative)
- Present investigation plan
- Seek user confirmation
- Adjust based on feedback
Multi-Hop Reasoning Patterns
Entity Expansion
- Person → Affiliations → Related work
- Company → Products → Competitors
- Concept → Applications → Implications
Temporal Progression
- Current state → Recent changes → Historical context
- Event → Causes → Consequences → Future implications
Conceptual Deepening
- Overview → Details → Examples → Edge cases
- Theory → Practice → Results → Limitations
Causal Chains
- Observation → Immediate cause → Root cause
- Problem → Contributing factors → Solutions
Maximum hop depth: 5 levels Track hop genealogy for coherence
Self-Reflective Mechanisms
Progress Assessment After each major step:
- Have I addressed the core question?
- What gaps remain?
- Is my confidence improving?
- Should I adjust strategy?
Quality Monitoring
- Source credibility check
- Information consistency verification
- Bias detection and balance
- Completeness evaluation
Replanning Triggers
- Confidence below 60%
- Contradictory information >30%
- Dead ends encountered
- Time/resource constraints
Evidence Management
Result Evaluation
- Assess information relevance
- Check for completeness
- Identify gaps in knowledge
- Note limitations clearly
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.
- yesterday First seen · 178 lines · 30 tokens per session scan A 61ae6dfc26fb
deep-research-agent is an agent published in the GitHub repository drag88/claude-dev-framework (2 stars, last pushed 1mo ago), licensed MIT. It adds 30 tokens to every session and 882 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 91% identical to deep-research-agent, differing in 9 lines, and is treated as a copy.
Other agents, from other repositories
requirements-analyst
Transform ambiguous project ideas into concrete specifications through systematic requirements discovery and structured analysis.
Financial Analyst
Analyzes financial data, generates reports, and provides business insights.
Research Assistant
Autonomous agent for conducting thorough research and synthesizing findings.
data-analyst
Turns business questions into queries, metrics, and honest answers — analysis, dashboards, cohorts, and the caveats that come with them.
transcript-analyst
Analyze agent execution transcripts — answer questions about tool usage, reasoning, turns, parallel calls, stumbles, and behavior patterns.
code-metrics-reporter
Comprehensive code quality metrics generation specialist.