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/tasksgit 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/tasks)<a href="https://agentmods.dev/commands/nguyenvanduocit/research-kit/tasks"><img src="https://agentmods.dev/badge/commands/nguyenvanduocit/research-kit/tasks.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.01353 |
| Opus 5 | $0.00004 | $0.00677 |
| Sonnet 5 | $0.00002 | $0.00271 |
| Haiku 4.5 | $0.00001 | $0.00135 |
Grade A, and why
tasks 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 — 138 lines — stays where its author put it; the contents beside it link to each section on GitHub.
User Input
$ARGUMENTS
Outline
This command breaks down the research methodology into specific, actionable tasks organized by phase. Run this after /research.methodology (and optionally /research.validate).
-
Quality Gate: AI Verification
This command has no setup script, so the quality gate runs entirely here. Read
methodology.mdanddefinition.md, then verify ALL of the following. If any REQUIRED check fails, STOP.CRITICAL checks (cannot bypass):
-
methodology.mdexists and has substantial content (not just template placeholders) -
definition.mdexists
REQUIRED checks (block unless user says "skip gate"):
- Research design type specified AND justified (reason given)
- At least 5 data sources identified, across at least 2 source types (academic, industry, government, etc.)
- Source quality criteria defined with tier system or CRAAP framework
- Credibility assessment framework documented
- Recency requirements specified (core literature timeframe + recent developments timeframe)
- Analysis approach matches research design type
- At least 2 bias mitigation strategies documented
- Limitations section has at least 3 acknowledged limitations
Output format:
QUALITY GATE: methodology → tasks (AI Verification) CRITICAL: ✓/✗ [check] REQUIRED: ✓/✗ [check] RESULT: PASSED / BLOCKEDIf BLOCKED: Tell user which checks failed, suggest
/research.methodologyto fix. -
-
Load methodology from
research/###-topic-name/methodology.md -
Load research definition from
research/###-topic-name/definition.md -
Generate task breakdown organized by research phases:
Phase 1: Setup & Preparation
- T001: Set up research directory structure
- T002: Initialize citation management (BibTeX file)
- T003: Document search terms and keywords
- T004: Identify key databases and sources
- T005: Set up research tools (if needed)
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 · 138 lines · 8 tokens per session scan A 1e9a2719ea9a
tasks 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,353 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.