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/jonathanmalkin/jules/researchnpx skills add jonathanmalkin/jules --skill researchgit clone --depth 1 https://github.com/jonathanmalkin/julesWrote 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/jonathanmalkin/jules/research)<a href="https://agentmods.dev/skills/jonathanmalkin/jules/research"><img src="https://agentmods.dev/badge/skills/jonathanmalkin/jules/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.00064 | $0.01725 |
| Opus 5 | $0.00032 | $0.00863 |
| Sonnet 5 | $0.00013 | $0.00345 |
| Haiku 4.5 | $0.00006 | $0.00172 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 188 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Research
Standalone research with living documents. Dispatches parallel agents, synthesizes sources, persists findings for cross-session pickup.
You are doing deep investigation. Thorough, source-driven, opinionated about what matters. Not a Wikipedia summary machine.
Cross-Session Persistence
Research documents live at Documents/Field-Notes/Research/YYYY-MM-DD-<Topic-Slug>.md. When a research request arrives:
- Check
Documents/Field-Notes/Research/for an existing file matching the topic (fuzzy match on filename) - If found: read it, present the existing document, and offer: "Continue from [date] or start fresh?"
- If not found: proceed to Phase 1
"Continue research on X" resumes from the Open Questions section of the existing document.
Phase 1: Topic Selection
If the user provides a topic directly (e.g., /research multi-agent systems), use that.
If no topic provided, ask: "What would you like me to research?"
Once a topic is confirmed, define a one-sentence scope: "Researching: [topic] — specifically [angle]." Confirm with the user if the scope is ambiguous.
Research Tool Selection
Pick the right tool for the query type:
See .claude/rules/search-tools.md for the full tool routing guide. Research-specific additions:
| Query Type | Tool | Why |
|---|---|---|
| Community discussion, opinions, experiences | Reddit MCP (search_reddit, get_post_details) |
Direct access to threads and comments |
| General web search, news, blog posts | WebSearch (built-in) | Broad coverage, keyword-based |
| Library docs, API references | Context7 (resolve-library-id → query-docs) |
Returns actual docs, prevents hallucinated APIs |
| Full page content extraction | WebFetch with a descriptive prompt | Prompt parameter guides extraction |
If Context7 isn't configured, fall back to WebSearch + WebFetch. Don't block on missing tools.
Phase 2: Research Dispatch
Launch up to 3 parallel Haiku subagents for data gathering. Each agent returns structured findings.
What ships with it
2 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.
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 · 188 lines · 64 tokens per session scan A a5ba04b24b1f
research is a skill published in the GitHub repository jonathanmalkin/jules (64 stars, last pushed 3mo ago), licensed MIT. It adds 64 tokens to every session and 1,725 once invoked, about $0.0003 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-30.
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…