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-triagegit 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-triage)<a href="https://agentmods.dev/skills/kevinzai/commander/ccc-triage"><img src="https://agentmods.dev/badge/skills/kevinzai/commander/ccc-triage/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-triage"><img src="https://agentmods.dev/badge/skills/kevinzai/commander/ccc-triage.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00076 | $0.01809 |
| Opus 5.5 | $0.00030 | $0.00724 |
| Sonnet 5.5 | $0.00015 | $0.00362 |
| Haiku 4.5 | $0.00008 | $0.00181 |
Grade A, and why
ccc-triage 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 — 147 lines — stays where its author put it; the contents beside it link to each section on GitHub.
$ccc-triage — GitHub issue and PR triage
CC Commander · $ccc-triage · read with gh, decide in the lead session, delegate deep reads, confirm every write
Triage follows the workflow-first doctrine in ../../rules/workflow-first.md: the lead session decides labels and priorities; bulk reading and per-item analysis are delegated.
When to use / when not to
- Use on a repo you maintain to sort open issues, decide PR direction, apply a label taxonomy, or get a one-screen digest.
- For reviewing one PR's code in depth, use
$ccc-code-review. - For tracker issues in Linear, use
$ccc-linear. - In Codex, ask each picker below as a plain-text question with the same options, and replace Agent/Workflow delegation with
codex execper batch.
What happens
1. Check prerequisites
gh auth status
gh repo view --json nameWithOwner -q .nameWithOwner
gh auth statusfails: tell the user to rungh auth login(interactive, browser) and stop.- Show the
nameWithOwnerand confirm it is the intended repo before any query; a worktree may point at a fork.
2. Action picker — AskUserQuestion
Skip when $ARGUMENTS is issues, prs, label or summary. Otherwise put the best match first and mark it 🟢: "pr", "pull request" or "merge" → Triage PRs; "label", "categorize" or "tag" → Auto-label; "summary", "digest", "overview" or "how many" → Summarize backlog; otherwise Triage issues.
question: "What do you want to triage?"
header: "Triage"
multiSelect: false
options:
- label: "🟢 Triage issues"
description: "Flag stale, unlabeled and needs-info issues; propose a label and priority each. Read-only."
- label: "Triage PRs"
description: "Flag draft, conflicting, CI-failing and stale PRs; propose merge or close. Read-only."
- label: "Auto-label"
description: "Apply the label taxonomy to untriaged items, one confirmed write at a time."
- label: "Summarize backlog"
description: "Counts by label, oldest items, no-response items, ready PRs. Read-only."
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 · +13 lines · +33 tokens per session c6249f99fdbc
- 1mo ago First seen · 134 lines · 43 tokens per session scan A aff5bbbca478
ccc-triage is a skill published in the GitHub repository KevinZai/commander (6 stars, last pushed yesterday), licensed MIT. It adds 76 tokens to every session and 1,809 once invoked, about $0.0003 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
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.
github-workflow
GitHub best practices for pull requests, code reviews, issues, Actions workflows, and repository management.
lerna
Best practices for Lerna monorepo management, versioning, and publishing.
stale-proposals
Audit this repository's local proposal queue for stale entries: proposals still marked proposed, deferred, or accepted even though the work already shipped, plus old proposals whose subject has become inert. Reconcile proposals against plugin changelogs and first-parent Git history, automatically resolve only…
apex-status
CTO-level project status from git and codebase state. Use when asked "where are we", "project status", "what's done", or at the start of a work session.
github-activity
Report what happened across GitHub repositories over a time window, read only. Invoke when the user asks what merged, which issues were opened or closed, or what moved between milestones since a date or since the last report, across one or more repositories.