Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/KevinZai/commandernpx agentmods add skills/kevinzai/commander/ccc-standupWrote 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-standup)<a href="https://agentmods.dev/skills/kevinzai/commander/ccc-standup"><img src="https://agentmods.dev/badge/skills/kevinzai/commander/ccc-standup.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.1 | $0.00048 | $0.00811 |
| Opus 5 | $0.00024 | $0.00405 |
| Sonnet 5 | $0.00010 | $0.00162 |
| Haiku 4.5 | $0.00005 | $0.00081 |
Grade A, and why
ccc-standup 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 — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
$ccc-standup — Standup generator
Placeholders like ~~source control refer to connected tools. See CONNECTORS.md.
Generate a standup update by pulling together recent activity across your tools. Standalone mode asks what you did. Connected mode pulls commits, issues, and PRs automatically.
Quick Mode (default)
If connectors are available, pull automatically and skip to output.
Standalone, ask one question: "What did you work on? (rough notes are fine — I'll structure them)"
Then generate the standup in the standard format below.
Optionally ask: "Any blockers?" — and incorporate the answer.
Power Mode
Activate by passing --power or detailed.
Full standup with:
- Yesterday: commits, PRs reviewed/merged, issues closed
- Today: planned work tied to open issues
- Blockers: with severity, owner, and suggested resolution
- Metrics: PRs merged, issues closed, lines changed (from ~~source control)
Auto-Pull Sources
When tools are connected, gather from:
- Git history —
git log --since="yesterday" --oneline --author="$(git config user.email)" - Session history — check
~/.claude/commander/sessions/for yesterday's session summaries - Knowledge base — check
~/.claude/commander/knowledge/for recent learnings
If Connectors Available
If ~~source control is connected:
- Pull commits from the last 24 hours (current user only)
- List PRs opened, reviewed, or merged
- Show CI/build status for active PRs
If ~~project tracker is connected:
- Pull issues moved to "In Progress" or "Done" since yesterday
- Show upcoming sprint items for "Today" section
- Flag any overdue issues as blockers
If ~~chat is connected:
- Scan for threads where your response is needed
- Include any team decisions made in chat as context
- Offer to post the standup directly to the team channel
Output Format
## Standup — [Date]
### Yesterday
- [Completed item — CC-42: Added OAuth support (merged PR #87)]
- [Completed item]
### Today
- [Planned item — CC-45: Fix webhook retry logic]
- [Planned item]
### Blockers
- [Blocker: API rate limiting on the payments provider — needs CC-48 resolved first]
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 · 97 lines · 48 tokens per session scan A 1aea38eb4d30
ccc-standup is a skill published in the GitHub repository KevinZai/commander (6 stars, last pushed yesterday), licensed MIT. It adds 48 tokens to every session and 811 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
debt-ops-add
Register a deferred decision in the tech-debt registry. Trigger by judgment, not a marker scan, whenever a future reader would ask "why this way?": an unmade decision, stub, loosened type, bypassed check, swallowed error, a default picked "for now", or a TODO/FIXME/HACK/XXX marker. Trigger immediately whenever you…
import
Import a tasks.md into the coco tracker as an epic with dependencies, and create matching issues in the configured issue tracker.
hotfix
Single-issue workflow for quick fixes and small changes that don't need full epic tracking. Creates a branch, implements the fix, commits with issue tracking, and closes.
debt-ops-review
Audit the tech-debt registry, rank survivors by churn × Fowler quadrant, surface a top-N list, then walk paydown on user follow-up. Use when the user asks to review debt, see what to pay down, work through entries, or check the debt registry. Stale entries drop with "drop A,B,C".
loki-mode
Multi-agent autonomous startup system for Claude Code. Triggers on "Loki Mode". Orchestrates 100+ specialized agents across engineering, QA, DevOps, security, data/ML, business operations, marketing, HR, and customer success. Takes PRD to fully deployed, revenue-generating product with zero human intervention.…
harness-step3-session-management
A project setup for keeping an agent’s work state in files between separate chat sessions. It creates a task list, a progress summary, and a script for checking the project environment.