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/dojogenesis/mcp/research-modesnpx skills add DojoGenesis/mcp --skill research-modesgit clone --depth 1 https://github.com/DojoGenesis/mcpWrote 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/dojogenesis/mcp/research-modes)<a href="https://agentmods.dev/skills/dojogenesis/mcp/research-modes"><img src="https://agentmods.dev/badge/skills/dojogenesis/mcp/research-modes.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.00051 | $0.03265 |
| Opus 5 | $0.00026 | $0.01632 |
| Sonnet 5 | $0.00010 | $0.00653 |
| Haiku 4.5 | $0.00005 | $0.00327 |
Grade A, and why
research-modes 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 — 431 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Research Modes Skill
Version: 1.2 Author: Tres Pies Design Purpose: Structured approaches for deep and wide research that produce actionable understanding, not just information.
I. Philosophy: Research Builds Understanding
Research isn't collecting information — it's building a mental model that enables decisions. If research doesn't change what you'd do next, it hasn't worked.
Three modes serve one goal:
- Deep Research (focused, 5 phases) finds answers
- Wide Research (broad, 4 phases) finds questions
- Research Synthesis (multi-file, 5 phases) finds patterns across sources
They are complementary. Wide research identifies where to dig. Deep research does the digging. Synthesis reveals what no single source can show. See the research-synthesis skill for the synthesis workflow.
II. When to Use This Skill
- Planning a new feature or system architecture
- Investigating a technical problem or design challenge
- Exploring competitive landscape or market trends
- Synthesizing learnings from multiple sources
- Making informed decisions based on evidence
Mode Selection
| Criteria | Deep Research | Wide Research | Research Synthesis |
|---|---|---|---|
| Scope | 1-3 related topics | 10-50+ topics | 3+ existing files |
| Sources per topic | 5-10+ | 1-3 | All provided files |
| Output | Detailed report with recommendation | Landscape map with opportunity matrix | Theme-based synthesis with cross-reference matrix |
| Use when | Decision depends on technical details | Exploring a new problem space | You have multiple files and need to find patterns across them |
III. The Research Workflows
Deep Research Mode (5 Phases)
Phase 1: Define Scope
Help the user narrow from topic to specific research question. A good research question is answerable, bounded, and actionable.
Bad: "What is the best database?" Good: "Which embedded database supports vector search with <100ms P95 latency for our Go backend?"
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 · 431 lines · 51 tokens per session scan A ea1a4d748b06
research-modes is a skill published in the GitHub repository DojoGenesis/mcp (0 stars, last pushed 1mo ago), licensed MIT. It adds 51 tokens to every session and 3,265 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-31.
Other skills, from other repositories
dd-code-generation
Use pup CLI for immediate Datadog operations or generate code for integration into applications.
drt-analyze
Analyze DRT cluster health for a given time range. Reconstructs the operations timeline, checks CockroachDB metrics (availability, latency, storage, changefeeds, jobs, goroutines, admission control, LSM, KV prober) and logs for anomalies, correlates findings with disruptive operations to distinguish expected…
redux-to-swr
Migrate React components from Redux + Saga to SWR hooks. Use when converting data fetching from Redux store (reducers, sagas, selectors, connect HOC) to SWR-based hooks in CockroachDB DB Console or cluster-ui.
prune-npm-overrides
Audit the pnpm overrides a repo already carries, remove the ones upstream has since fixed, and require a justification comment on every one that stays. The counterpart to fix-npm-vulnerability. Use when asked to check, clean up, or prune the overrides, or when an override's tracking issue comes up for review.
mma-investigator
Expert system for investigating MMA (Multi-Metric Allocator) behavior on CockroachDB clusters. Helps oncall engineers diagnose load imbalances, understand rebalancing decisions, and identify why MMA did or didn't act.
file-crdb-issue
Use when filing, creating, or reporting GitHub issues for CockroachDB. Use when asked to open a bug report, feature request, investigation issue, or performance inquiry. Also use when the user mentions wanting to track a problem, report a regression, or document unexpected behavior in CockroachDB.