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 commands/kevinzai/commander/ccc-lineargit 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-linear)<a href="https://agentmods.dev/commands/kevinzai/commander/ccc-linear"><img src="https://agentmods.dev/badge/commands/kevinzai/commander/ccc-linear.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 | $0.00019 | $0.00438 |
| Opus 5 | $0.00010 | $0.00219 |
| Sonnet 5 | $0.00004 | $0.00088 |
| Haiku 4.5 | $0.00002 | $0.00044 |
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 yesterday.
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.
What it actually says
/ccc-linear — Linear Board
Open your Linear project board directly in CCC. View issues by status, pick one to work on, or create new ones.
What This Command Does
- Connects to Linear using your
LINEAR_API_KEY_PERSONALenv var - Shows your project board: In Progress, Todo, Backlog, Done
- Progress bar showing completion percentage
- Pick an issue to start working on (auto-assigns, starts session)
- Create new issues directly from CCC
Setup
- Get a Linear API key: linear.app/settings/api
- Set it:
export LINEAR_API_KEY_PERSONAL=lin_api_xxxxx - Run
ccc> Settings > Linear Setup > Choose your team and project - Done. The board will load automatically.
Usage
/ccc-linear # Open the board
ccc > Linear Board # Same thing via menu
Board View
─── Linear Board ───────────────────
████████████████░░░░░░ 18/24 done
In Progress (2)
CC-61 Remotion hero video
CC-62 README overhaul
Todo (3)
CC-48 Foundation + submodules
CC-49 Vendor scanner
Backlog (1)
CC-50 Showstopper CLI UI
Done: 18 issues
Actions
- Pick an issue — assigns to you, moves to In Progress, starts a CCC session
- Create issue — quick title + description, auto-adds to project
- Refresh — reload the board
Session Integration
When you pick an issue and build:
- CCC creates a session linked to the Linear issue
- Progress comments auto-posted to the issue
- Session completion auto-moves issue to Done
- Cost and duration tracked on the issue
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.
- yesterday First seen · 64 lines · 19 tokens per session scan A ae328bd9ec46
ccc-linear is a command published in the GitHub repository KevinZai/commander (6 stars, last pushed yesterday), licensed MIT. It adds 19 tokens to every session and 438 once invoked, about $0.0001 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 commands, from other repositories
whats-next
Show current project status and suggest next steps.
from-plan
Convert a Claude Code plan (or any spec file) into a task file and optionally hand it off to Cursor.
specmanager-build
Build one phase of a SpecManager feature's plan via the builder subagent. Stops at the phase boundary; never advances.
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.
roadmap
Generate or update a per-release roadmap from the PRD and analysis documents. Triages features, groups into phases, and produces a structured roadmap.