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 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/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/kevinzai/commander/ccc-research"><img src="https://agentmods.dev/badge/skills/kevinzai/commander/ccc-research.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00060 | $0.01500 |
| Opus 5.5 | $0.00024 | $0.00600 |
| Sonnet 5.5 | $0.00012 | $0.00300 |
| Haiku 4.5 | $0.00006 | $0.00150 |
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 6d 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 — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.
$ccc-research — research, routed
CC Commander · $ccc-research · a cited answer, a comparison or a spec before any code is written.
Research sub-skills (deep-research, spec-interview, cross-model-review, literature-review, competitive-analysis, data-ingestion, trend-analysis, large-context) ship with the Commander CLI toolkit. Invoke one with the Skill tool when it is listed in this session; otherwise apply the method in references/routing.md. The user's selected model is preserved.
Codex: ask pickers as plain-text questions, run parallel lanes as separate codex exec calls, and write the report to a file.
When to use / when not to
- Use before a non-trivial build, for "which library/tool/vendor", "what are the trends in X", "interview me for a spec", "review this decision from several angles", or an input too large to read in one pass.
- Use
$ccc-brainstormfor open-ended ideation,$ccc-debatefor a structured for/against verdict on one decision,$ccc-planonce the spec exists,$ccc-datafor data pipelines and analytics.
What happens
1. Route by intent, or ask
An argument or a clear intent routes straight to the sub-skill in references/routing.md. "Research X before building" runs the research-before-build sequence in step 4.
Otherwise ask with AskUserQuestion (header "Research"), recommended first:
- 🟢 Deep research — parallel sources, citations, a synthesized report
- Compare options —
competitive-analysisfeature and trade-off table - Spec interview — 5 to 7 questions, then a written spec
- More — cross-model review, literature review, trends, or ingest something large (a follow-up picker)
2. Fix the question
Restate the question in one sentence, the depth (overview, detailed, exhaustive), sources to include or exclude, and the output (brief, report, table). Ask only for what changes the result.
3. Gather and synthesize
- Deep research: when
/deep-researchis listed in this session, invoke it with the Skill tool (/deep-research <question>); it fans out search, fact-checks and returns a cited report. Otherwise split the question into 3 to 5 independent sub-questions and run them as parallel Agent calls (each returns findings with source URLs and dates, never raw page dumps), using WebSearch and WebFetch. Synthesize in the lead context. - Cross-model review: Claude and the Codex CLI only. Run an independent Claude reviewer through the Agent tool, and Codex when installed:
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 6d ago Changed · +31 lines · +25 tokens per session fef6d9a62132
- 1mo ago 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 today), licensed MIT. It adds 60 tokens to every session and 1,500 once invoked, about $0.0002 per session on Opus 5.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
knowledgebase
Generate professional multi-page HTML knowledge bases and study guides for software engineering, data science, and AI/ML work — field guides, solution handbooks, service catalogs, team runbooks, onboarding documentation, and technical study resources. Produces self-contained, offline-capable HTML sites with sidebar…
quiz-me
Use right after writing or editing code or files for the user — before ending your turn — to quiz them on what was just built and confirm they actually understand it. Also triggers on "quiz me", "test my understanding", "check what I learned", "comprehension check", or recovering the understanding that vaporizes when…
self-assessment
Interactive skill assessment with personalized learning path generation.
course-material-creator
Create custom educational materials including syllabi, lesson plans, assessments, reading lists, and learning objectives. Use when building course curricula, training programs, workshops, or educational content.
learn-teach
Step-by-step explanation of a concept with progressive depth.
agent-code-explainer
Specialist subagent: Explains complex code in clear, understandable terms. Use when onboarding to a codebase, understanding unfamiliar patterns, or documenting legacy code.