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 agentmods add skills/kevinzai/commander/ccc-linearnpx skills add KevinZai/commander --skill ccc-lineargit clone --depth 1 https://github.com/KevinZai/commanderWhat 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 | $0.00040 | $0.01740 |
| Opus 5 | $0.00020 | $0.00870 |
| Sonnet 5 | $0.00008 | $0.00348 |
| Haiku 4.5 | $0.00004 | $0.00174 |
Grade A, and why
ccc-linear 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 2d 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 — 182 lines — stays where its author put it; the contents beside it link to each section on GitHub.
$ccc-linear — Linear Board
View your board, pick an issue, or create a new one — all click-first.
Promoted from commands/ccc-linear.md (legacy slash command).
Response shape (EVERY time)
1. Brand header
**CC Commander** · Linear Integration · [Docs](https://commanderplugin.com)
2. Context strip
Detect in parallel via a single Bash call:
- Check CLAUDE.md for a Linear team reference (grep "team" or "CC-")
- Check for
.linear/config file in repo root env | grep -c LINEAR_API_KEY→ is the key set?- Check if any
mcp__linear__*tool is available (Linear MCP connected?)
Render:
🎟️ Team:
<detected team or 'unknown'>· MCP: <connected | not connected> · key: <set | missing>
If MCP not connected AND no API key: add line — "→ Run $ccc-connect to wire Linear first."
3. Action picker — AskUserQuestion
question: "What do you want to do?"
header: "Linear"
multiSelect: false
options:
- label: "📋 View my open issues"
description: "Top 10 issues assigned to you, grouped by status."
preview: "(per-context: 'You have N in progress, M in todo')"
- label: "🎯 Pick one to work on"
description: "Grab the top issue, create a branch, start."
preview: "Recommended — goes from ticket → branch in one click."
- label: "✨ Create a new issue"
description: "Quick title + description, auto-add to project."
preview: "For ideas that shouldn't live in your head."
- label: "🗺️ Board overview"
description: "Columns: In Progress / Todo / Backlog / Done. Progress bar."
preview: "Best for standups and status updates."
Prepend ⭐ to "Pick one to work on" unless user has zero open issues — then default to "Create a new issue".
Handle the selection
View my open issues
Use mcp__linear__list_issues (via mcp__83782f74-...__list_issues naming in tool ids). Filter by assignee=me, state.type in ("started", "unstarted").
Render:
### 🎟️ My open issues
**🔄 In Progress (2)**
- CC-61 · Remotion hero video
- CC-62 · README overhaul
**📋 Todo (3)**
- CC-48 · Foundation + submodules
- CC-49 · Vendor scanner
- CC-50 · Showstopper CLI UI
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.
- 2d ago First seen · 182 lines · 40 tokens per session scan A 6a384b8eb53e
ccc-linear is a skill published in the GitHub repository KevinZai/commander (6 stars, last pushed 3d ago), licensed MIT. It adds 40 tokens to every session and 1,740 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-08-31.
Other skills, from other repositories
agent-memory
../../../engineering/agent-memory/skills/agent-memory/SKILL.md.
agile-product-owner
../../../product-team/agile-product-owner/skills/agile-product-owner/SKILL.md.
rulesync
Generates and syncs AI rule configuration files (.cursorrules, CLAUDE.md, copilot-instructions.md) across 20+ coding tools from a single source. Use when syncing AI rules, running rulesync commands, importing or generating rule files, or managing shared AI coding configurations.
agent-workspace-linux
Use when a task needs an isolated hidden Linux desktop or workspace-owned browser: GUI app QA, web/browser/shopping automation, sandboxed app observation, or stale workspace cleanup. Routes agent-workspace-linux MCP tools on demand. Does NOT apply to host desktop/Chrome control, generic MCP setup, or pure code/file…
loongsuite-pilot-insight
基于 LoongSuite Pilot / AI Coding Agent 日志生成事件洞察、组织洞察、数据质量、研发效能和 AI Native 使用类 SLS 报表时使用；包含 AI Coding 事件表语义，以及团队报表可选的部门维表、deptuser 组织关系、指标口径和公共 CTE，通常与 sls-dashboard-builder 一起使用。.
map-review
Interactive 4-section code review using monitor, predictor, and evaluator agents plus the user and maintainer role reviewers on current changes. Use when reviewing a diff, PR, or staged work before merge. Do NOT use to plan or implement; use map-plan or map-efficient.