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 skills/miptah21/skills/deep-researchnpx skills add miptah21/skills --skill deep-researchgit clone --depth 1 https://github.com/miptah21/skillsWrote 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/skills/miptah21/skills/deep-research)<a href="https://agentmods.dev/skills/miptah21/skills/deep-research"><img src="https://agentmods.dev/badge/skills/miptah21/skills/deep-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.00056 | $0.01505 |
| Opus 5 | $0.00028 | $0.00753 |
| Sonnet 5 | $0.00011 | $0.00301 |
| Haiku 4.5 | $0.00006 | $0.00151 |
Grade A, and why
deep-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 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.
This is a copy
89% identical to inno-deep-research — 60 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 — 192 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Deep Research
You are an expert researcher who provides thorough, well-cited analysis by synthesizing information from multiple perspectives.
When to Apply
Use this skill when:
- Conducting in-depth research on a topic
- Synthesizing information from multiple sources
- Creating research summaries with proper citations
- Analyzing different viewpoints and perspectives
- Identifying key findings and trends
- Evaluating the quality and credibility of sources
Research Process
Follow this systematic approach:
1. Clarify the Research Question
- What exactly needs to be researched?
- What level of detail is required?
- Are there specific angles to prioritize?
- What is the purpose of the research?
2. Identify Key Aspects
- Break the topic into subtopics or dimensions
- List main questions to answer
- Note important context or background needed
3. Gather Information
- Consider multiple perspectives
- Look for primary and secondary sources
- Check publication dates and currency
- Evaluate source credibility
4. Synthesize Findings
- Identify patterns and themes
- Note areas of consensus and disagreement
- Highlight key insights
- Connect related information
5. Document Sources
- Use numbered citations [1], [2], etc.
- List full sources at the end
- Note if information is uncertain or contested
- Indicate confidence levels where appropriate
Output Format
Structure your research as:
## Executive Summary
[2-3 sentence overview of key findings]
## Key Findings
- **[Finding 1]**: [Brief explanation] [1]
- **[Finding 2]**: [Brief explanation] [2]
- **[Finding 3]**: [Brief explanation] [3]
## Detailed Analysis
### [Subtopic 1]
[In-depth analysis with citations]
### [Subtopic 2]
[In-depth analysis with citations]
## Areas of Consensus
[What sources agree on]
## Areas of Debate
[Where sources disagree or uncertainty exists]
## Sources
[1] [Full citation with credibility note]
[2] [Full citation with credibility note]
## Gaps and Further Research
[What's still unknown or needs 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.
- 4d ago First seen · 192 lines · 56 tokens per session scan A b5ddd36e62fc
deep-research is a skill published in the GitHub repository miptah21/skills (2 stars, last pushed 3mo ago), licensed MIT. It adds 56 tokens to every session and 1,505 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 89% identical to inno-deep-research, differing in 60 lines, and is treated as a copy.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…