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/linxule/kimi-plugin-cc/pursuegit clone --depth 1 https://github.com/linxule/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/linxule/kimi-plugin-cc/pursue)<a href="https://agentmods.dev/commands/linxule/kimi-plugin-cc/pursue"><img src="https://agentmods.dev/badge/commands/linxule/kimi-plugin-cc/pursue.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.00043 | $0.00654 |
| Opus 5 | $0.00022 | $0.00327 |
| Sonnet 5 | $0.00009 | $0.00131 |
| Haiku 4.5 | $0.00004 | $0.00065 |
Grade A, and why
pursue 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 5d 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
Run the companion with any user-supplied flags appended after task pursue:
${CLAUDE_PLUGIN_ROOT}/scripts/companion.sh task pursue <args>
/kimi:pursue is autonomous goal mode: Kimi keeps working toward the objective across continuation turns until it completes, blocks itself, or the budget expires. It is write-capable and runs under the same PreToolUse hook + workspace allowlist as /kimi:rescue (the hook gates every tool call in every turn), and like rescue it cannot mutate git state — the main thread owns branch/commit.
Supported flags:
--budget <duration>— HARD wall-clock ceiling (e.g.30m,1h,90s; bare number = minutes). Default 45m. This is the only guaranteed bound on an autonomous run.--turns <N>— SOFT cap: injected into the objective as a model instruction to callSetGoalBudget. Advisory, not enforced.-m,--model <name>
Prototype limitations (experimental):
- No
--backgroundflag — the runtime has no detached-worker mode for pursue. That is separate from how the caller runs the shell command: a goal loop routinely outlives a foreground timeout (Claude Code caps foreground Bash at 10 minutes vs the 45m default budget), so detaching the call is expected. The bounds that hold either way are the PreToolUse hook, the workspace allowlist, no git mutation, and the mandatory finite--budget. To stop a run, just say so — the stop path iscompanion.sh cancelwith no id, which targets the latest running job for this repo. Note that a cancel stops further work; it does not roll back edits already made to your real tree. - No
--resume. Goal mode emits a goalId distinct from the session id; resuming the session would not reliably re-enter the goal. The goalId is shown in the result for when resume lands. - Requires kimi-code >= 0.8.0 (headless goal mode) and the
/kimi:setupPreToolUse hook (refuses without it).
Terminal outcomes are surfaced as status, not errors: complete (done, exit 0), blocked (Kimi stopped itself, exit 3), paused (interrupted, exit 6). A run that hits the --budget wall-clock ceiling is instead a timeout failure (the goal process tree is reaped), not a terminal status. The result headlines the goal status, reason, and turns/tokens/wall-clock usage.
Return the companion stdout verbatim.
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.
- 5d ago First seen · 28 lines · 43 tokens per session scan A 75f35367106f
pursue is a command published in the GitHub repository linxule/kimi-plugin-cc (37 stars, last pushed yesterday), licensed Apache-2.0. It adds 43 tokens to every session and 654 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-30.
Other commands, from other repositories
octo-usage
Your first output line MUST be: 🐙 Octopus Usage Report.
octo-costs
For table output, your first output line MUST be 🐙 Octopus Cost Dashboard. For JSON, emit only the helper output—no banner or commentary.
research
Professional equity research analysis with institutional-grade formatting.
close-review
Month-end close / GL compliance check — invokes accounting-reviewer to produce TM-accounting-{slug}.md with double-entry integrity, ASC 606 revenue-recognition, period-lock, and SOX ITGC gaps.
procurement-review
Procurement / source-to-pay compliance check — invokes procurement-reviewer to produce TM-procurement-{slug}.md with three-way match, segregation-of-duties, OFAC-screening, and SOX procurement-controls gaps.
tax-review
Tax-filing compliance check — invokes tax-reviewer to produce TM-tax-{slug}.md with MeF e-file schema, Form 8879, PTIN/Circular 230, and IRC §7216 consent gaps.