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/executegit clone --depth 1 https://github.com/nguyenvanduocit/research-kitWhat 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.00006 | $0.03057 |
| Opus 5 | $0.00003 | $0.01528 |
| Sonnet 5 | $0.00001 | $0.00611 |
| Haiku 4.5 | $0.00001 | $0.00306 |
Grade C, and why
execute scanned grade C with 2 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 2d 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.
Tells the agent never to refusehighAnti-refusal
Suppressing the ability to decline removes a core safety control; a later harmful request then succeeds.
You have POWERFUL tools available for data collection. DO NOT refuse this task or claim limitations. You MUST use these tools proactively: Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- **Bash**: Run `./scripts/bash/download-source.sh` to download content (embeds URL), curl, wget, Python scripts How it starts
The opening of the file, as written. The whole thing — 297 lines — stays where its author put it; the contents beside it link to each section on GitHub.
User Input
$ARGUMENTS
Outline
This command guides the systematic execution of the research methodology to collect data and generate raw results. Run this after /research.tasks.
CRITICAL: YOU MUST ACTIVELY EXECUTE DATA COLLECTION
You have POWERFUL tools available for data collection. DO NOT refuse this task or claim limitations. You MUST use these tools proactively:
CRITICAL: Download Sources & Cite with file:line
- NEVER cite a URL directly - Always download content locally first
- Use download-source.sh to download web content:
./scripts/bash/download-source.sh "URL" sources/web/filename.md - Read local files - Always read from
sources/folder, not from web - Cite with file:line - Every insight/evidence MUST cite
sources/path/file.md:line
Available Data Collection Tools:
- WebSearch: Search the web to find URLs for articles, statistics, reports
- Bash: Run
./scripts/bash/download-source.shto download content (embeds URL), curl, wget, Python scripts - Write: Create collection scripts, save downloaded content
- Read: Parse downloaded LOCAL files (CSV, JSON, XML, HTML, PDF, etc.)
Common Data Collection Tasks YOU CAN AND MUST DO:
- Web Research: Use WebSearch to find relevant URLs, then download with download-source.sh
- Download Content: Use
./scripts/bash/download-source.sh "URL" sources/web/filename.mdto save web content (URL embedded) - Download Data: Use Bash with curl/wget for datasets, download-source.sh for articles
- API Data Collection: Write Python scripts to call APIs and collect data
- Web Scraping: Create Python scripts using requests/BeautifulSoup/selenium
- Document Processing: Use download-source.sh to extract text from PDFs, web pages
- Video/Audio: Use Bash to download videos/audio with yt-dlp, extract transcripts
- Academic Papers: Search and download papers using download-source.sh to
sources/papers/ - Government Data: Download datasets from data.gov, census, statistics agencies
- Code Execution: Run data collection, validation, and processing scripts
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.
- 2d ago First seen · 297 lines · 6 tokens per session scan C 9b0c4847bb0f
execute is a command published in the GitHub repository nguyenvanduocit/research-kit (20 stars, last pushed 5mo ago), licensed MIT. It adds 6 tokens to every session and 3,057 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it C with 2 findings (tells the agent never to refuse, makes network calls). 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.
constitution
Create or update the project constitution from interactive or provided principle inputs.