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 skills add jakkaj/tools --skill deepresearch-v2git clone --depth 1 https://github.com/jakkaj/toolsWrote 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/jakkaj/tools/deepresearch-v2)<a href="https://agentmods.dev/skills/jakkaj/tools/deepresearch-v2"><img src="https://agentmods.dev/badge/skills/jakkaj/tools/deepresearch-v2/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/skills/jakkaj/tools/deepresearch-v2"><img src="https://agentmods.dev/badge/skills/jakkaj/tools/deepresearch-v2.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.00029 | $0.00579 |
| Opus 5.5 | $0.00012 | $0.00232 |
| Sonnet 5.5 | $0.00006 | $0.00116 |
| Haiku 4.5 | $0.00003 | $0.00058 |
Grade A, and why
deepresearch-v2 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 — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Please deep think / ultrathink as this is a complex task.
deepresearch-v2
Craft a structured research prompt to leverage a deep research agent for solving coding challenges. Domain-aware: surfaces boundary concerns and cross-domain impacts when relevant.
Pre-flight: Load Domain Context
Before crafting the prompt, check for domain context:
- If
docs/domains/registry.mdexists → scan registered domains - If
docs/domains/domain-map.mdexists → note domain relationships and contract edges - For domains related to the problem → read
docs/domains/<slug>/domain.md(concepts, contracts, composition)
If no domain system is present, skip this step and proceed normally.
Crafting the Research Prompt
Please create a structured prompt with the following sections:
1. Clear Problem Definition
- Precisely define the issue we are facing.
- Include relevant error messages, stack traces, or problematic behaviors.
- Which domain(s) does this problem affect? Does it cross domain boundaries?
- If multi-domain: which domain owns the fix vs. which domains are impacted?
2. Contextual Information
- Specify the technology stack involved (languages, frameworks, libraries).
- Include exact versions of key dependencies and any recent updates.
- Mention any recent codebase changes potentially related to the problem.
- Note domain-specific dependencies: contracts consumed, contracts exposed, shared infrastructure.
- Flag domain separation concerns — is the problem caused by tight coupling across boundaries?
3. Key Research Questions
- Identify clear, actionable research questions to guide the deep research agent.
- Ensure these questions target resolving our current challenge directly.
- If domains are involved: Does the solution respect existing domain boundaries? Should a contract be introduced or modified?
4. Recommended Tools and Resources
- List specific tools, libraries, or methodologies we should investigate.
- Include any helpful links or references.
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 · 70 lines · 29 tokens per session scan A e2506e8116e6
deepresearch-v2 is a skill published in the GitHub repository jakkaj/tools (5 stars, last pushed 24d ago), licensed MIT. It adds 29 tokens to every session and 579 once invoked, about $0.0001 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-08-31.
deepresearch-v2 compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| deepresearch-v2jakkaj/tools | Skill | 5 | 24d ago | MIT | A | 29 | Claude Code, Codex |
| imagegenopenai/codex | Skill | 134k | today | Apache-2.0 | A | 113 | Codex |
| local-ai-agentsmicrosoft/ai-agents-for-beginners | Skill | 79k | yesterday | MIT | A | 200 | Claude Code, Codex |
| playwright-climicrosoft/playwright | Skill | 100k | yesterday | Apache-2.0 | A | 19 | Claude Code |
| browser-automationopenclaw/openclaw | Skill | 394k | today | MIT | A | 36 | Claude Code |
| systematic-debuggingobra/superpowers | Skill | 314k | 4d ago | MIT | A | 21 | Claude Code |
| next-cache-components-adoptionvercel/next.js | Skill | 143k | yesterday | MIT | A | 95 | Claude Code |