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.
git 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/commands/kevinzai/commander/ccc-office-hours)<a href="https://agentmods.dev/commands/kevinzai/commander/ccc-office-hours"><img src="https://agentmods.dev/badge/commands/kevinzai/commander/ccc-office-hours/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/commands/kevinzai/commander/ccc-office-hours"><img src="https://agentmods.dev/badge/commands/kevinzai/commander/ccc-office-hours.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.00050 | $0.00983 |
| Opus 5.5 | $0.00020 | $0.00393 |
| Sonnet 5.5 | $0.00010 | $0.00197 |
| Haiku 4.5 | $0.00005 | $0.00098 |
Grade A, and why
ccc-office-hours 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 8d 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 — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/ccc-office-hours — validate before you build
CC Commander · /ccc-office-hours · one honest verdict on an idea, and a planning brief when it is worth building.
Idea: $ARGUMENTS
Run a skeptical validation session. The aim is to kill weak ideas fast and sharpen strong ones. Be direct, give reasons, and do not cheerlead.
Step 1: Understand the idea
Use the idea from $ARGUMENTS or the conversation. If it is missing or vague, ask the user for two or three sentences covering:
- What are you building?
- Who is it for?
- Why now?
Do not continue until the idea is clear.
Step 2: Product lens
- Who is this for? Name a specific persona; "developers" is too broad.
- What problem does it solve? Real pain or nice-to-have? How do users solve it today?
- What is the MVP? The simplest version that delivers value, and what can be cut.
- Build or buy? Which existing solutions exist, and why not use or extend them?
- Cost of inaction? What happens if this is never built? Sometimes the answer is nothing.
Step 3: Technical lens
- Complexity: low, medium or high, and why.
- Dependencies: new libraries, services or APIs it introduces.
- Blast radius: what breaks if it goes wrong, and which existing functionality is at risk.
- Reversibility: one-way door or two-way door; how hard is it to undo?
- Maintenance burden: who maintains it in six months, and what ongoing cost or toil it adds.
Where the idea touches an existing codebase, check these answers against the code (Grep, Read) instead of guessing, and cite the files.
Step 4: User lens
- Discovery: how does the user find it; obvious or buried?
- Happy path: the ideal flow in one paragraph.
- Error path: what goes wrong and how the user recovers.
- Cognitive load: does it make the product simpler or more complex?
- One-sentence test: can the feature be explained in one sentence? If not, it is too complicated.
Step 5: Verdict
Deliver exactly one:
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.
- 8d ago Changed · +10 lines · +17 tokens per session b434a02e6352
- 1mo ago First seen · 94 lines · 33 tokens per session scan A 027d023fb180
ccc-office-hours is a command published in the GitHub repository KevinZai/commander (6 stars, last pushed today), licensed MIT. It adds 50 tokens to every session and 983 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-04.
Other commands, from other repositories
execute
Execute the next available tracked task with TDD, pre-commit validation, PR creation, AI code review, and issue tracker bridge sync.
phase
Orchestrate a full roadmap phase. Designs features, imports to tracker, creates issues, then executes.
dashboard
Compact visual progress dashboard with progress bar, task table, dependency graph, and active/blocked/next status.
status
Show current execution status with progress, dependencies, file ownership, and parallelization opportunities.
sync
Reconcile coco tracker state with the configured issue tracker. Syncs task statuses and reports mismatches.
planning-triage
Quick-score an enhancement, bug, or feedback item using the impact-first triage framework. Creates an issue if approved.