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 commands/nguyenvanduocit/research-kit/methodologygit clone --depth 1 https://github.com/nguyenvanduocit/research-kitWrote 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/commands/nguyenvanduocit/research-kit/methodology)<a href="https://agentmods.dev/commands/nguyenvanduocit/research-kit/methodology"><img src="https://agentmods.dev/badge/commands/nguyenvanduocit/research-kit/methodology.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.00008 | $0.01222 |
| Opus 5 | $0.00004 | $0.00611 |
| Sonnet 5 | $0.00002 | $0.00244 |
| Haiku 4.5 | $0.00001 | $0.00122 |
Grade A, and why
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 3d 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 — 143 lines — stays where its author put it; the contents beside it link to each section on GitHub.
User Input
$ARGUMENTS
Outline
This command generates a comprehensive research methodology based on the research definition. Run this after /research.define (and optionally /research.refine).
IMPORTANT: The setup script (scripts/bash/setup-methodology.sh) will automatically:
- Create methodology directory structure
- Initialize methodology template (
methodology.md) - Set up supporting document templates (literature review, data sources, ethics)
- Verify prerequisite phases have been completed (especially
definition.md)
DO NOT manually create these directories or files - the script {SCRIPT} handles everything!
-
Run the methodology setup script
{SCRIPT}which will set up all required files and verify prerequisites -
Load research definition from
research/###-topic-name/definition.md -
Quality Gate: AI Verification (after script gate passes)
Read
definition.mdand verify ALL of the following. Output each check result. If any REQUIRED check fails, STOP and report to user. User can say "skip gate" to override (log bypass in output).REQUIRED checks (block workflow):
- At least 1 primary research question + 3 sub-questions defined
- Scope has both "included" and "excluded" items, each with at least 3 items
- At least 5 success criteria with measurable metrics
- Zero unresolved
[NEEDS CLARIFICATION]markers - Research type is justified (not just selected, but reason explained)
RECOMMENDED checks (warn only):
- Ethical considerations section present with content
- Expected deliverables listed
- Time boundaries defined
Output format:
QUALITY GATE: define → methodology (AI Verification) REQUIRED: ✓/✗ [check description] ... RECOMMENDED: ✓/⚠ [check description] RESULT: PASSED / BLOCKED (N REQUIRED failed)If BLOCKED: Tell user which checks failed, suggest
/research.defineor/research.refineto fix. Do NOT proceed.
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.
- 3d ago First seen · 143 lines · 8 tokens per session scan A 4df21792b454
methodology is a command published in the GitHub repository nguyenvanduocit/research-kit (20 stars, last pushed 5mo ago), licensed MIT. It adds 8 tokens to every session and 1,222 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it A with 0 findings. It comes from a forked repository.
Other commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.