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 yachi/claude-skills --skill deep-researchgit clone --depth 1 https://github.com/yachi/claude-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/yachi/claude-skills/deep-research)<a href="https://agentmods.dev/skills/yachi/claude-skills/deep-research"><img src="https://agentmods.dev/badge/skills/yachi/claude-skills/deep-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/skills/yachi/claude-skills/deep-research"><img src="https://agentmods.dev/badge/skills/yachi/claude-skills/deep-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.00164 | $0.03821 |
| Opus 5 | $0.00082 | $0.01911 |
| Sonnet 5 | $0.00033 | $0.00764 |
| Haiku 4.5 | $0.00016 | $0.00382 |
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 10d 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 — 201 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/dr — Deep Research
You are now in Deep Research mode. The standard: ICD 203 analytic tradecraft (9/9 standards), GRADE evidence hierarchy, NIST reproducibility. Every claim survives cross-examination by the foremost domain expert. No hand-waving. No unverified assertions. If you can't prove it, you don't say it.
Core Principles
-
Evidence over reasoning — Your internal knowledge is a starting hypothesis, never a conclusion. Every factual claim must be verified through tool use (WebSearch, WebFetch, Bash, code execution, MCP tools) against authoritative external sources.
-
Quantitative over qualitative — Wherever possible, replace adjectives with numbers. "Faster" becomes "47% lower p99 latency (benchmarked)." "More popular" becomes "3.2M weekly downloads vs 180K." "More secure" becomes "0 CVEs in 3 years vs 12 (4 critical)."
-
Standards over opinions — Every domain has authoritative standards bodies, best practices, and regulatory frameworks. Find them. Cite them. Compare the subject against them.
-
Adversarial rigor — Before presenting conclusions, actively try to disprove them. The strongest argument is one that has survived its best counterargument.
Research Protocol
Phase 0: Clarify (if needed)
If the query is ambiguous or underspecified, ask 1-2 clarifying questions before committing to research. Skip if the question is already clear and specific.
Phase 1: Decompose
Break the research question into orthogonal sub-questions. For each sub-question, identify:
- What specifically needs to be answered
- What type of evidence would be conclusive (benchmark data, standards compliance, expert consensus, regulatory text, academic study)
- Where that evidence is most likely found
Do this decomposition explicitly — write it out so the user can see your research plan.
Premise validation (kill switch): Identify the core premise. Quick-search to verify it holds before investing in all phases. If it doesn't, pivot immediately and tell the user. A fast pivot based on evidence saves enormous wasted effort and is more valuable than a thorough analysis built on a false premise.
What ships with it
60 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- autoresearch/evolve-v1.md 3.5 KB
- autoresearch/evolve-v2.md 4.0 KB
- autoresearch/examples/adversarial-rust-vs-go.md 18 KB
- autoresearch/examples/best-thorium-msr-25-25.md 25 KB
- autoresearch/examples/best-zk-proofs-25-25.md 17 KB
- autoresearch/examples/failure-cms-pricing-19-25.md 25 KB
- autoresearch/examples/good-ptsd-therapy-23-25.md 17 KB
- autoresearch/examples/premise-killed-blockchain-healthcare.md 18 KB
- autoresearch/log.md 124 KB
- autoresearch/outputs/run-1.md 25 KB
- autoresearch/outputs/run-10.md 19 KB
- autoresearch/outputs/run-11.md 22 KB
- autoresearch/outputs/run-12.md 25 KB
- autoresearch/outputs/run-13.md 19 KB
- autoresearch/outputs/run-14.md 24 KB
- autoresearch/outputs/run-15.md 23 KB
- autoresearch/outputs/run-16.md 16 KB
- autoresearch/outputs/run-17.md 18 KB
- autoresearch/outputs/run-18.md 20 KB
- autoresearch/outputs/run-19.md 19 KB
- autoresearch/outputs/run-2.md 26 KB
- autoresearch/outputs/run-20.md 20 KB
- autoresearch/outputs/run-21.md 20 KB
- autoresearch/outputs/run-22.md 22 KB
- autoresearch/outputs/run-23.md 21 KB
- autoresearch/outputs/run-24.md 22 KB
- autoresearch/outputs/run-25.md 23 KB
- autoresearch/outputs/run-26.md 18 KB
- autoresearch/outputs/run-27.md 21 KB
- autoresearch/outputs/run-28.md 23 KB
- autoresearch/outputs/run-29.md 23 KB
- autoresearch/outputs/run-3.md 18 KB
- autoresearch/outputs/run-30-judge.md 3.3 KB
- autoresearch/outputs/run-30.md 20 KB
- autoresearch/outputs/run-31.md 27 KB
- autoresearch/outputs/run-32.md 27 KB
- autoresearch/outputs/run-33.md 27 KB
- autoresearch/outputs/run-34.md 28 KB
- autoresearch/outputs/run-35.md 19 KB
- autoresearch/outputs/run-36.md 24 KB
- autoresearch/outputs/run-37.md 22 KB
- autoresearch/outputs/run-38.md 20 KB
- autoresearch/outputs/run-39.md 23 KB
- autoresearch/outputs/run-4.md 22 KB
- autoresearch/outputs/run-40.md 22 KB
- autoresearch/outputs/run-41.md 26 KB
- autoresearch/outputs/run-42.md 24 KB
- autoresearch/outputs/run-43.md 24 KB
- autoresearch/outputs/run-44.md 24 KB
- autoresearch/outputs/run-45.md 20 KB
- autoresearch/outputs/run-46-judge.md 4.3 KB
- autoresearch/outputs/run-46.md 25 KB
- autoresearch/outputs/run-47.md 22 KB
- autoresearch/outputs/run-48.md 22 KB
- autoresearch/outputs/run-49.md 24 KB
- autoresearch/outputs/run-5.md 25 KB
- autoresearch/outputs/run-50.md 21 KB
- autoresearch/outputs/run-51.md 20 KB
- autoresearch/outputs/run-52.md 20 KB
- autoresearch/outputs/run-53.md 21 KB
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.
- 10d ago First seen · 201 lines · 164 tokens per session scan A 72d87fe40118
deep-research is a skill published in the GitHub repository yachi/claude-skills (3 stars, last pushed 5mo ago), licensed MIT. It adds 164 tokens to every session and 3,821 once invoked, about $0.0008 per session on Opus 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.
Other skills, from other repositories
cco-tools
Show what tools actually cost in tokens — learned per-tool averages from observed results, replacing the hardcoded MCP/Agent guesses.
cco-clean
Clean up old tracking data and reset statistics.
skill-creator-plus
Create, test, evaluate, and improve Claude skills — and answer questions about how skills work. Use for "create a skill", "make a skill for", "write a SKILL.md", "turn this into a skill", "run evals", "test/benchmark my skill", "optimize my skill description", "improve triggering", "A/B test my skill", "blind…
openclaw-setup
Set up, install, configure, and deploy OpenClaw (formerly ClawdBot/MoltBot) — a personal AI assistant that runs on your own devices and connects to messaging channels. Use when users ask to "set up OpenClaw," "install ClawdBot," "install MoltBot," "deploy a personal AI assistant," "configure OpenClaw on Mac," "deploy…
cpp-reinforcement-learning
C++ Reinforcement Learning best practices using libtorch (PyTorch C++ frontend) and modern C++17/20. Use when: Implementing RL algorithms in C++ for performance-critical applications Building production RL systems with libtorch Creating replay buffers and experience storage Optimizing RL training with GPU acceleration…
fp-yoohoo
Terminal-recall mode. Reference for fp-yoohoo, the plugin that brings the terminal window to the foreground when Claude Code stops and waits on a human: a permission prompt, a question dialog, a plan to approve. Explains what it hooks, which desktops it can raise a window on, how the already-focused guard works, and…