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/classmethod/tsumiki/kairo-loopgit clone --depth 1 https://github.com/classmethod/tsumikiWhat 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.00046 | $0.00519 |
| Opus 5 | $0.00023 | $0.00260 |
| Sonnet 5 | $0.00009 | $0.00104 |
| Haiku 4.5 | $0.00005 | $0.00052 |
Grade A, and why
kairo-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 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
- $1 がない場合、「引数に要件名・開始TASK-ID・終了TASK-IDを指定してください（例: /kairo-loop ユーザー認証システム TASK-00001 TASK-00005）」と言って終了する
- $2 がない場合、「引数に開始TASK-IDを指定してください（例: TASK-00001）」と言って終了する
- $3 がない場合、「引数に終了TASK-IDを指定してください（例: TASK-00005）」と言って終了する
$0 の $1 から順番に実行してください。 $2 まで完了したら一旦終了して。 以下の作業を実施してください
- /tsumiki-legacy:kairo-implement を理解して、skillの内容に正確に従ってください
- 実施する内容を全てtodoに詳細に記録してください。
- 品質確認の段階で戻る処理をするときは以下の手順を組み込んでください
- 品質の確認処理
- 戻り先決定ルールを品質確認後の戻る処理内に含めてください
- 戻り先からのステップをそれぞれtodoに追加(例:step-e追加の場合は、step-e,step-f,step-g,品質確認を追加する)
- 追加したtodoの依存関係を設定
- 戻り先として追加したtaskに遷移する
- 最後のチェックボックスを入れる作業も含めて忘れずにtodoに追加してください
- todoには必ず依存関係を設定してください
- todoに記録が終わったら順番に実施してください
- 全ての TASK の完了が終わったら
/tsumiki:auto-debugを実行する
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 · 25 lines · 46 tokens per session scan A 56d3b7168a71
kairo-loop is a command published in the GitHub repository classmethod/tsumiki (974 stars, last pushed 25d ago), licensed MIT. It adds 46 tokens to every session and 519 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
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.