Borrowing it
Nothing to install: this file belongs to apokamo/kaji. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/apokamo/kaji/main/.claude/skills/issue-verify-design/SKILL.mdgit clone --depth 1 https://github.com/apokamo/kajiWrote 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/apokamo/kaji/issue-verify-design)<a href="https://agentmods.dev/skills/apokamo/kaji/issue-verify-design"><img src="https://agentmods.dev/badge/skills/apokamo/kaji/issue-verify-design/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/skills/apokamo/kaji/issue-verify-design"><img src="https://agentmods.dev/badge/skills/apokamo/kaji/issue-verify-design.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00036 | $0.02392 |
| Opus 5 | $0.00018 | $0.01196 |
| Sonnet 5 | $0.00007 | $0.00478 |
| Haiku 4.5 | $0.00004 | $0.00239 |
Grade A, and why
issue-verify-design 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.
How it starts
The opening of the file, as written. The whole thing — 228 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Issue Verify Design
重要: このスキルは設計/修正を行ったセッションとは 別のセッション で実行することを推奨します。 同一セッションで実行すると、設計時のバイアスが確認判断に影響する可能性があります。
設計修正後の確認を行います。
重要: このコマンドは「指摘事項が適切に修正されたか」のみを確認します。 新規の指摘は行いません。これはレビューサイクルの収束を保証するためです。
いつ使うか
| タイミング | このスキルを使用 |
|---|---|
/issue-fix-design 後の修正確認 |
✅ 必須 |
| 新規レビューが必要な場合 | ❌ /issue-review-design を使用 |
ワークフロー内の位置: design → review-design → (fix → verify) → implement
入力
ハーネス経由（コンテキスト変数）
常に注入される変数:
| 変数 | 型 | 説明 |
|---|---|---|
issue_id |
str | 正規化済み Issue ID（GitHub 数値または local ID） |
issue_ref |
str | 人間可読の Issue 参照（GitHub では #<issue_id>、local では bare ID） |
step_id |
str | 現在のステップ ID |
条件付きで注入される変数:
| 変数 | 型 | 条件 | 説明 |
|---|---|---|---|
cycle_count |
int | サイクル内ステップのみ | 現在のイテレーション番号 |
max_iterations |
int | サイクル内ステップのみ | サイクルの上限回数 |
手動実行（スラッシュコマンド）
$ARGUMENTS = <issue_id>
解決ルール
コンテキスト変数 issue_id が存在すればそちらを使用。
なければ $ARGUMENTS の第1引数を issue_id として使用。
issue_ref はハーネス経由ではプロンプトに自動注入される（prompt.py 側で provider 別に整形）。手動実行時は issue_id から導出する: GitHub 数値 ID なら #<issue_id>、local-* 形式なら bare ID（# を付けない）。
前提知識の読み込み
以下のドキュメントを Read ツールで読み込んでから作業を開始すること。
- テスト規約:
docs/dev/testing-convention.md - コーディング規約:
docs/reference/python/python-style.md- 必要に応じて
docs/reference/python/naming-conventions.md/type-hints.md/docstring-style.md/error-handling.md/logging.mdを追加読込
- 必要に応じて
- 開発ワークフロー:
docs/dev/development_workflow.md
verify と review の違い
| 項目 | review | verify |
|---|---|---|
| 目的 | フルレビュー | 修正確認のみ |
| 新規指摘 | する | しない |
| 確認範囲 | 設計全体 | 前回指摘箇所のみ |
| 使用タイミング | 設計完了後 | fix 後 |
共通ルール
- _shared/report-unrelated-issues.md — 作業中に発見した無関係な問題の報告ルール
実行手順
Step 1: コンテキスト取得
-
_shared/worktree-resolve.md の手順に従い、Worktree の絶対パスを取得。
-
前回の指摘内容を取得:
kaji issue view [issue_id] --comments「設計レビュー結果」と「設計修正報告」を確認。
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 · 228 lines · 36 tokens per session scan A d0a23a99674b
issue-verify-design is a skill published in the GitHub repository apokamo/kaji (12 stars, last pushed yesterday), licensed Apache-2.0. It adds 36 tokens to every session and 2,392 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
software-design-lifecycle-solution-design-biz-arch-diagramming
A method for designing and reviewing a business-solution architecture: a middle-level view that connects confirmed business problems to a solution before technical implementation is designed.
software-design-lifecycle-tech-overview-system-arch-diagramming
A guide for architects who draw or review system architecture diagrams during overview design. It explains subsystems, outside dependencies, communication links, and system boundaries without going into every technology detail.
creative-claude-design
Design one-off HTML artifacts (landing, deck, prototype).
diagram-drawio
Use when the user requests diagrams, flowcharts, architecture diagrams, ER diagrams, UML / sequence / class diagrams, network topology, ML/DL model figures (Transformer/CNN/LSTM), mind maps, or any visualization. Also use proactively when explaining systems with 3+ components, complex data flows, or relationships that…
diagram-architecture
Dark-themed SVG architecture/cloud/infra diagrams as HTML.
software-design-lifecycle-tech-overview-functional-arch-diagramming
A method for creating or reviewing a system functional architecture diagram: a high-level picture of what the system does and how its capabilities are grouped. It focuses on user and business capabilities, not code, deployment, or step-by-step runtime behavior.