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 skills/classmethod/tsumiki/kairo-implementnpx skills add classmethod/tsumiki --skill kairo-implementgit 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.01818 |
| Opus 5 | $0.00023 | $0.00909 |
| Sonnet 5 | $0.00009 | $0.00364 |
| Haiku 4.5 | $0.00005 | $0.00182 |
Grade A, and why
kairo-implement 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 2d 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.
How it starts
The opening of the file, as written. The whole thing — 129 lines — stays where its author put it; the contents beside it link to each section on GitHub.
あなたは実装担当者です。残タスクを調べて、指定されたコマンドを駆使して実装をしてください
context
要件名={{requirement_name}}(引数または Claude Codeタスクから取得) TASK-ID={{task_id}}(引数または Claude Codeタスクから取得) hilモード={{hil}}(--hil オプション指定時は true) defaultModel={{defaultModel}}(--model オプション) thinkModelName={{thinkModelName}}(--think-model オプション。デフォルト: opus) tddModelName={{tddModelName}}(--tdd-model オプション。デフォルト: sonnet) noteModelName={{noteModelName}}(--note-model オプション。デフォルト: haiku)
コマンド選択ルール:
- thinkTaskName: thinkModelName が指定されていれば thinkModelName / defaultModel が指定されていれば defaultModel / それ以外は opus
- tddTaskName: tddModelName が指定されていれば tddModelName / defaultModel が指定されていれば defaultModel / それ以外は sonnet
- noteTaskName: noteModelName が指定されていれば noteModelName / defaultModel が指定されていれば defaultModel / それ以外は haiku
step
- context の内容をまとめてユーザに宣言する
- step0 を実行する
step0: Claude Codeタスクシステムの確認
- TaskList で未完了のタスク(pending/in_progress)を確認する
- subject が "TASK-" で始まるタスクを抽出し、各タスクを TaskGet で詳細を取得する
- metadata から requirement_name / task_file / phase / task_type を取得する
- 引数の優先順位:
- 要件名が引数で指定されている場合: 引数の要件名を使用
- 引数省略の場合: Claude Codeタスクの metadata から取得
- TASK-ID が引数で指定されている場合: 引数の TASK-ID を使用
- 引数省略の場合: blockedBy が空かつ status=pending の最初のタスクを選択
- 選択した Claude Codeタスクの ID を claude_task_id として記録する
step1 を実行する
step1: 追加ルールの読み込み
docs/spec/{要件名}/note.mdが存在する場合は Read ツールで読み込む
step2 を実行する
step2: プロジェクト文書の読み込み
以下のファイルを Read ツールで読み込む(存在するものを優先):
docs/tasks/{要件名}/overview.mdまたはdocs/tasks/{要件名}-overview.mddocs/tasks/{要件名}/TASK-{task_id}.mdまたはdocs/tasks/{要件名}-tasks.md- Claude Codeタスクの metadata に task_file がある場合はそのパスを優先使用
- 依存タスクのファイルも読み込み、実装の順序と関連性を理解する
step3 を実行する
step3: タスクの選択と実行開始
- 選択されたタスクの詳細を表示する
- TaskUpdate でステータスを 'in_progress' に更新する
- "📌 Claude Codeタスク #{{claude_task_id}} を実行中に設定しました" を表示する
step4 を実行する
step4: 依存関係の確認
- Claude CodeタスクのblockedByフィールドを確認する
- 依存タスクが完了しているか確認する(status=completed)
- 未完了の依存タスクがある場合は警告を表示してユーザーに確認する
step5 を実行する
step5: 実装ディレクトリの準備
- 現在のワークスペースで必要に応じてディレクトリ構造を確認する
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2d ago First seen · 129 lines · 46 tokens per session scan A cc1b27106358
kairo-implement is a skill published in the GitHub repository classmethod/tsumiki (974 stars, last pushed 25d ago), licensed MIT. It adds 46 tokens to every session and 1,818 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
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…