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 richardcb/oh-my-gemini --skill research-methodologygit clone --depth 1 https://github.com/richardcb/oh-my-geminiWrote 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/richardcb/oh-my-gemini/research-methodology)<a href="https://agentmods.dev/skills/richardcb/oh-my-gemini/research-methodology"><img src="https://agentmods.dev/badge/skills/richardcb/oh-my-gemini/research-methodology/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/richardcb/oh-my-gemini/research-methodology"><img src="https://agentmods.dev/badge/skills/richardcb/oh-my-gemini/research-methodology.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.00044 | $0.00637 |
| Opus 5 | $0.00022 | $0.00318 |
| Sonnet 5 | $0.00009 | $0.00127 |
| Haiku 4.5 | $0.00004 | $0.00064 |
Grade A, and why
research-methodology 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 — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Research Methodology Skill
Goal
Guide systematic research with structured output. Find, verify, and synthesize technical information into actionable research briefs.
Activation Triggers
This skill should be activated when:
- User includes
research:or@researcherin their prompt - Task requires finding external documentation or best practices
- User needs to investigate APIs, libraries, or technical concepts
- Comparative analysis of approaches is needed
When NOT to Use
- User wants code written (use implementation instead)
- Simple questions answerable from local codebase
- Bug fixes or debugging (use debug-assistant)
Research Process
1. Understand the Need
Clarify what specific information is being sought:
- API documentation?
- Implementation examples?
- Best practices or patterns?
- Troubleshooting guidance?
- Competitive/alternative analysis?
2. Search Strategically
Prioritize sources by reliability:
- Official documentation
- Code examples from reputable repositories
- Technical blogs from known experts
- Community discussions (StackOverflow, GitHub Issues)
- General web results (verify carefully)
3. Verify Quality
For every finding:
- Check the publication date (recent is usually better for tech)
- Cross-reference with at least one other source
- Prefer sources with code examples over theory-only
- Note any version-specific caveats
4. Synthesize Clearly
Don't dump raw search results. Organize findings into:
- Key concepts explained simply
- Relevant code snippets (tested if possible)
- Gotchas and common mistakes
- Links for deeper reading
Output Format: Research Brief
## Research Brief: [Topic]
### Summary
[2-3 sentence overview of findings]
### Key Findings
#### 1. [Finding Title]
[Explanation with context]
**Code Example:**
```[language]
[relevant code]
2. [Finding Title]
[Explanation]
Gotchas & Common Mistakes
- [Mistake 1]: [How to avoid]
- [Mistake 2]: [How to avoid]
Recommendations
Based on research, the recommended approach is: [Specific recommendation with rationale]
Sources
- [URL 1]: [What it provided]
- [URL 2]: [What it provided]
Open Questions
- [Questions that need further research or user input]
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 · 110 lines · 44 tokens per session scan A eebe82ad7c5c
research-methodology is a skill published in the GitHub repository richardcb/oh-my-gemini (16 stars, last pushed 6mo ago), licensed MIT. It adds 44 tokens to every session and 637 once invoked, about $0.0002 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
intuitive-tests
Use this skill whenever the user asks about unit test best practices, test organization, flat test suites, redundant tests, test refactors, pytest/JUnit/Jest/xUnit layout, test taxonomy, flaky tests, coverage quality, fixtures, mocks, parametrization, pruning existing UTs, or "which tests are worth keeping." It…
intuitive-preflight
Turn a vague task, plan, issue, or "LGTM/go ahead" request into an approval-ready preflight contract before implementation starts. Use when the user wants prompt preflight, clearer scope, non-goals, context package, acceptance criteria, definition of done, verification, stop gates, the exact execution command, or…
skill-runner
Run a bounded development task through named skills in an isolated, tmux-backed Codex or Claude session. Use for durable or artifact-sensitive worker phases, supervised skill runs, and post-run skill evaluation.
intuitive-doc
Create and maintain an intuitive human documentation surface for AI-agent-developed repos. Use when humans should only need README.md, ARCHITECTURE.md, STATUS.md, and docs/human/ while planning logs, generated docs, retrospectives, ADR detail, and implementation evidence stay in AI-agent-only folders.
intuitive-shape
Shape a raw product or project idea into a bounded decision before planning or implementation. Use when deciding whether an idea deserves a bet, setting an appetite, comparing candidate bets under finite capacity, cutting scope, exposing rabbit holes and no-gos, or choosing BET, RESEARCH, RESHAPE, or PASS. This skill…
create-migration
Create and manage Entity Framework Core database migrations including schema changes, seed data, and rollback strategies. Use when adding or modifying EF Core entities, setting up a new DbContext, applying data seeding, running dotnet ef commands, or troubleshooting migration conflicts.