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.
git clone --depth 1 https://github.com/luanmorenommaciel/kimi-plugin-ccWrote 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/luanmorenommaciel/kimi-plugin-cc/crank-next)<a href="https://agentmods.dev/commands/luanmorenommaciel/kimi-plugin-cc/crank-next"><img src="https://agentmods.dev/badge/commands/luanmorenommaciel/kimi-plugin-cc/crank-next/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/commands/luanmorenommaciel/kimi-plugin-cc/crank-next"><img src="https://agentmods.dev/badge/commands/luanmorenommaciel/kimi-plugin-cc/crank-next.svg" alt="Reviewed on agentmods" width="80" 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.00019 | $0.00227 |
| Opus 5 | $0.00010 | $0.00113 |
| Sonnet 5 | $0.00004 | $0.00045 |
| Haiku 4.5 | $0.00002 | $0.00023 |
Grade A, and why
kimi:crank-next 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 9d 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.
What it actually says
/kimi:crank-next
Pick and run the next ready task from the backlog.
Usage
/kimi:crank-next
/kimi:crank-next --skip-preflight
/kimi:crank-next --model kimi-code/k3
Process
- Scan
tasks/for specs withstatus: ready - Select highest priority (P0 > P1 > P2) whose
depends_onare all completed - Dispatch via broker with preflight + origin-state gates
- Return session ID and task summary
Notes
- If no tasks are ready, exits with message "No ready tasks"
- Honors
--force-dispatchand--skip-preflightoverrides
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.
- 9d ago First seen · 31 lines · 0 tokens per session scan A 28f2360db9e6
kimi:crank-next is a command published in the GitHub repository luanmorenommaciel/kimi-plugin-cc (12 stars, last pushed 1mo ago), licensed MIT. It adds 19 tokens to every session and 227 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-08-31.
Other commands, from other repositories
template
Manage issue templates for streamlined issue creation.
sync-linear
Sync current work with Linear ticket status.
add-note
Add an internal or external note to a ConnectWise PSA ticket.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
dispatcher
Pick the next-best repo to work on across the portfolio — rank free repos, recommend one, claim its lease atomically, and route to the entry command.
workpm
A project-management workflow for coordinating multiple AI workers through five stages. It includes task assignment, shared activity logs, worker replacement, and final checks.