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 luanmorenommaciel/kimi-plugin-cc --skill crank-loopgit 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/skills/luanmorenommaciel/kimi-plugin-cc/crank-loop)<a href="https://agentmods.dev/skills/luanmorenommaciel/kimi-plugin-cc/crank-loop"><img src="https://agentmods.dev/badge/skills/luanmorenommaciel/kimi-plugin-cc/crank-loop.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.00511 |
| Opus 5 | $0.00022 | $0.00255 |
| Sonnet 5 | $0.00009 | $0.00102 |
| Haiku 4.5 | $0.00004 | $0.00051 |
Grade A, and why
crank-loop 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.
What it actually says
The Crank Loop
A reproducible process for autonomous, supervised agent cranking. One cycle:
- PREP — isolate work (git worktree or clean branch off origin).
- SPEC — write a task spec (
tasks/T-*.md): goal, success criteria, anti-patterns,touches_paths, and a runnable# Exit Checkbash block. - GATE — only delegate specs whose evals are runnable and side-effect-free.
- CRANK — execute the spec (e.g.
/crank:run), preferring background execution for long tasks. - MEASURE — capture duration, tokens/cost, tool-call mix, and eval pass/fail for every run.
- DIAGNOSE — root-cause every defect; adversarially review the result (
/crank:challenge). - DESIGN — decide the fixes; plan them (
/crank:plan). - APPLY — implement fixes with tests.
- SHIP — commit, tag, release.
- SCORE — re-crank a fresh task and score against the rubric; repeat until ≥ 9/10.
Scoring rubric
| Dimension | Weight |
|---|---|
| Work correctness (task done right) | 25% |
| Isolation (edits land in the right tree) | 20% |
| State preservation (no lost/zombie sessions) | 15% |
| Telemetry (every run measurable) | 15% |
| Scope discipline (no creep) | 15% |
| Auto-commit (work lands committed) | 10% |
Hard-won rules
- A hung crank must die: always run with a wall-clock cap AND an idle-output watchdog; a timeout is terminal, never retried.
- Sessions must be resumable natively (
kimi --session <id>) — prompt-text "continue" hacks lose context. - Tokens come from the session's real usage records, never from char-count estimates, when available.
- Read-only roles are a behavior contract (review/explore never write); enforce in the prompt and verify in review.
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 First seen · 38 lines · 43 tokens per session scan A 3dd0546b858a
crank-loop is a skill published in the GitHub repository luanmorenommaciel/kimi-plugin-cc (12 stars, last pushed 1mo ago), licensed MIT. It adds 43 tokens to every session and 511 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…