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 skills/kevinzai/commander/ccc-researchnpx skills add KevinZai/commander --skill ccc-researchgit clone --depth 1 https://github.com/KevinZai/commanderWrote 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/kevinzai/commander/ccc-research)<a href="https://agentmods.dev/skills/kevinzai/commander/ccc-research"><img src="https://agentmods.dev/badge/skills/kevinzai/commander/ccc-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.00035 | $0.00798 |
| Opus 5 | $0.00017 | $0.00399 |
| Sonnet 5 | $0.00007 | $0.00160 |
| Haiku 4.5 | $0.00003 | $0.00080 |
Grade A, and why
ccc-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 yesterday.
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 — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
$ccc-research — Research domain hub
Load ONE skill. Get the entire research domain. 8 skills in one.
Sub-Skills
| # | Skill | Focus |
|---|---|---|
| 1 | deep-research | Multi-source research with parallel agents, citation tracking, synthesis |
| 2 | spec-interview | 5-7 structured questions to produce a complete spec before coding |
| 3 | cross-model-review | Code/decision review using multiple AI models for diverse perspectives |
| 4 | literature-review | Academic/technical literature review with source evaluation |
| 5 | competitive-analysis | Competing products/tools/libraries feature comparison |
| 6 | data-ingestion | Ingest and summarize large documents, codebases, or datasets |
| 7 | trend-analysis | Technology, market, or usage pattern trend analysis |
| 8 | large-context | Opus 5's native 1M window, reduction, chunk-and-synthesize, then Codex CLI for mechanical execution |
Research Surfaces
In addition to web search, research can use connected channels as surfaces:
- Telegram/Discord channels — community sentiment, ecosystem news, real-time signals
- Files API — ingest uploaded documents, codebases, or data files directly
- Cross-model review — route to multiple models for independent perspectives
No expressed intent? Present the top 3 sub-skills + "More…" as an AskUserQuestion picker (≤4 options).
Routing Matrix
| Your Intent | Route To |
|---|---|
| "Research X before building" | deep-research + competitive-analysis |
| "Define spec first" / "Interview me" | spec-interview |
| "Review this from multiple angles" | cross-model-review |
| "Literature review" / "Academic sources" | literature-review |
| "Compare these tools/libraries" | competitive-analysis |
| "Summarize this large document" | data-ingestion |
| "What are the trends in X?" | trend-analysis |
| "File too large for context" | large-context |
Protocol: Research Before Build
The recommended sequence for any non-trivial feature:
deep-research→ find existing solutions, prior art, best practicescompetitive-analysis→ evaluate optionsspec-interview→ define requirements before writing code- Hand off to implementation skills with research context
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.
- yesterday First seen · 76 lines · 35 tokens per session scan A 3146fe05649f
ccc-research is a skill published in the GitHub repository KevinZai/commander (6 stars, last pushed yesterday), licensed MIT. It adds 35 tokens to every session and 798 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-09-03.
Other skills, from other repositories
interview-me
Conduct an adaptive interactive interview on any topic and produce a structured markdown report, summary, or implementation plan. Use when the user says "interview me", "interview me about", "run an interview on", "help me think through", or wants guided discovery on any subject. Also triggers on "talk me through"…
data-structures
Reference for advanced data structure patterns used in competitive programming and technical interviews. Covers heaps, monotonic stacks, tries, segment trees, Fenwick trees, stack-based parsing, and ordered sets with Python templates, recognition signals, and edge case guidance.
dp-patterns
Reference for dynamic programming patterns — recognition signals, constraint mapping, Python templates, edge cases, and common mistakes for 8 core DP techniques.
math-and-combinatorics
Reference patterns for mathematical and combinatorial problem-solving. Covers modular arithmetic, prime sieves, GCD/LCM, binomial coefficients, fast exponentiation, counting techniques, inclusion-exclusion, and game theory. Load this skill when a problem involves number theory, combinatorics, modular operations, or…
search-and-optimization
Reference patterns for search, optimization, and greedy algorithms. Covers binary search (classic and on-answer), two pointers, sliding window, greedy strategies, prefix sums, merge intervals, and monotonic stack. Use when solving problems that involve searching sorted data, optimizing over constraints, processing…
string-algorithms
Reference for string algorithm patterns — KMP, Z-function, Rabin-Karp, Manacher's, string hashing, suffix arrays, and Aho-Corasick. Covers recognition signals, core ideas, Python templates, edge cases, and common mistakes for each technique.