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/shakestzd/contextune/ctx-researchgit clone --depth 1 https://github.com/shakestzd/contextuneWrote 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/shakestzd/contextune/ctx-research)<a href="https://agentmods.dev/commands/shakestzd/contextune/ctx-research"><img src="https://agentmods.dev/badge/commands/shakestzd/contextune/ctx-research.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.00025 | $0.01800 |
| Opus 5 | $0.00013 | $0.00900 |
| Sonnet 5 | $0.00005 | $0.00360 |
| Haiku 4.5 | $0.00003 | $0.00180 |
Grade A, and why
ctx:research 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 — 282 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Contextune Research - Quick Technical Investigation
Conduct focused research using 3 parallel Haiku agents to answer specific technical questions quickly.
Use Cases
- "What's the best React state library in 2025?"
- "Should I use REST or GraphQL for this API?"
- "What testing frameworks work with Python 3.12?"
- "Does our codebase already handle authentication?"
How It Works
- You ask a research question
- 3 parallel agents execute (1-2 min total):
- Agent 1: Web Research - Latest trends, comparisons, best practices
- Agent 2: Codebase Search - Existing patterns, reuse opportunities
- Agent 3: Dependency Analysis - What's installed, compatibility
- Synthesis - Combined findings with recommendation
- Result - Comparison table + actionable next steps
Agent Specifications
Agent 1: Web Research
Searches the web for current information:
Research {QUESTION} using WebSearch.
Current date: {CURRENT_DATE}
Tech stack: {TECH_STACK}
Search queries:
- '{QUESTION} best practices {CURRENT_YEAR}'
- '{QUESTION} comparison latest'
- '{QUESTION} recommendations {CURRENT_YEAR}'
Report format (<500 words):
1. **Top 3 Options Found**
2. **Comparison Table** (pros/cons for each)
3. **Current Trends** (what's popular/recommended)
4. **Recommendation** with reasoning
Focus on recent information (2024-2025 preferred).
Expected output: Comparison of top solutions with pros/cons
Agent 2: Codebase Search
Searches existing code for patterns:
Search codebase for existing solutions to {QUESTION}.
Use Grep/Glob to find:
- Similar functionality: grep -r '{KEYWORDS}' .
- Relevant files: glob '**/*{pattern}*'
- Existing implementations
**CRITICAL**: If similar code exists, recommend REUSING it!
Report format (<400 words):
1. **Existing Functionality** (file:line references)
2. **Patterns to Follow** (coding style, architecture)
3. **Recommendation**:
- REUSE: If good solution exists
- NEW: If nothing suitable found
- ENHANCE: If partial solution exists
Include specific file paths and line numbers.
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 · 282 lines · 25 tokens per session scan A 9aace4cdd103
ctx:research is a command published in the GitHub repository shakestzd/contextune (5 stars, last pushed 8mo ago), licensed MIT. It adds 25 tokens to every session and 1,800 once invoked, about $0.0001 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 commands, from other repositories
opsx-bulk-apply
Apply multiple OpenSpec changes concurrently in isolated worktrees.
opsx-propose
Propose a new change - create it and generate all artifacts in one step.
opsx-apply
Implement tasks from an OpenSpec change (Experimental).
opsx-sync
Sync delta specs from a change to main specs.
opsx-archive
Archive a completed change in the experimental workflow.
opsx-verify
Verify implementation matches change artifacts before archiving.