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.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.00043 | $0.01499 |
| Opus 5 | $0.00022 | $0.00749 |
| Sonnet 5 | $0.00009 | $0.00300 |
| Haiku 4.5 | $0.00004 | $0.00150 |
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 3d 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 — 134 lines — stays where its author put it; the contents beside it link to each section on GitHub.
$ccc-triage — GitHub Issue & PR Triage
Maintainer-grade triage for the plugin's GitHub repo. Uses the gh CLI to list, label, and summarize open issues and pull requests — and can hand off deep, per-item triage to a Sonnet agent or Codex when the backlog is large.
CC Commander · Maintainer Tools · Docs
Triage follows the workflow-first doctrine (
commander/cowork-plugin/rules/workflow-first.md): the lead session decides labels and priorities; bulk reading and per-item analysis are delegated.
What this does
Four click-first actions, each backed by gh:
- Triage issues — list open issues, surface stale/unlabeled/needs-info, propose a label + priority per item.
- Triage PRs — list open PRs, flag draft/conflicting/CI-failing/stale, propose merge-or-close direction.
- Auto-label — apply a consistent label taxonomy (bug/feat/docs/question/good-first-issue) across untriaged items.
- Summarize backlog — one-screen digest: counts by label, oldest items, no-response items, ready-to-merge PRs.
Prerequisites
ghauthenticated: rungh auth status. If not logged in, the user runsgh auth login(browser, interactive).- A repo context: this skill targets the current repo (
ghinfersowner/repofrom the cwd's git remote). Confirm withgh repo view --json nameWithOwner -q .nameWithOwnerbefore acting.
Picker
Call AskUserQuestion so the user picks the triage action:
question: "What do you want to triage?"
header: "Triage"
multiSelect: false
options:
- label: "🐛 Triage issues"
description: "List open issues, flag stale/unlabeled/needs-info, propose a label + priority each."
preview: "gh issue list --state open --json number,title,labels,createdAt,comments"
- label: "🔀 Triage PRs"
description: "List open PRs, flag draft/conflicting/CI-failing/stale, propose merge-or-close."
preview: "gh pr list --state open --json number,title,isDraft,mergeable,statusCheckRollup"
- label: "🏷️ Auto-label"
description: "Apply a consistent label taxonomy across untriaged items. Confirms before each write."
preview: "gh issue edit <n> --add-label <label> (one confirm per item)."
- label: "📊 Summarize backlog"
description: "One-screen digest: counts by label, oldest items, no-response items, ready PRs."
preview: "Read-only roll-up. No writes."
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.
- 3d 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 today), licensed MIT. It adds 43 tokens to every session and 1,499 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
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.
moai-workflow-worktree
Git worktree management for parallel SPEC development with isolated workspaces, automatic branch registration, and seamless MoAI-ADK integration. Use when setting up parallel development environments.
gitlab-ops
Use this skill when performing VCS operations on GitLab or GitHub repositories — creating, updating, or closing issues and MRs, applying label taxonomy, running glab/gh CLI commands, or resolving project paths dynamically. Acts as the single source of truth for CLI command syntax and label conventions; consuming…
gitlab-portfolio
Use when you need a single-pane cross-repo health view across all vault-registered GitLab and GitHub projects. Discovers repos from overview.md frontmatter in /01-projects//, aggregates open issues, MRs, critical labels, and stale signals via parallel glab/gh calls, then writes an idempotent PORTFOLIO.md dashboard.…
session-end
Use this skill when performing a full session close-out: verifies all planned work against the agreed plan, creates issues for gaps, runs quality gates, commits cleanly, mirrors to GitHub, and produces a session summary. Triggered by /close command.
session-start
Use this skill when initializing a session for any project repo. Autonomously analyzes git state, VCS issues, SSOT files, branches, environment, and cross-repo status. Then presents structured findings with recommendations for user alignment before creating a wave plan. Triggered by /session…