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/i-doc-final-check/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/i-doc-final-check)<a href="https://agentmods.dev/skills/apokamo/kaji/i-doc-final-check"><img src="https://agentmods.dev/badge/skills/apokamo/kaji/i-doc-final-check/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/i-doc-final-check"><img src="https://agentmods.dev/badge/skills/apokamo/kaji/i-doc-final-check.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.00038 | $0.01178 |
| Opus 5 | $0.00019 | $0.00589 |
| Sonnet 5 | $0.00008 | $0.00236 |
| Haiku 4.5 | $0.00004 | $0.00118 |
Grade A, and why
i-doc-final-check 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 10d 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 — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.
I Doc Final Check
docs-only workflow の PR 前最終ゲート。 現行実装、CLI、運用方針、workflow 定義との整合を確認し、docs-only として PR に進めるかを判定する。
いつ使うか
| タイミング | このスキルを使用 |
|---|---|
/i-doc-review または /i-doc-verify で Approve 後 |
✅ 必須 |
ワークフロー内の位置: i-doc-update → i-doc-review → i-doc-final-check → i-pr → close
入力
ハーネス経由（コンテキスト変数）
常に注入される変数:
| 変数 | 型 | 説明 |
|---|---|---|
issue_id |
str | 正規化済み Issue ID（GitHub 数値または local ID） |
issue_ref |
str | 人間可読の Issue 参照（GitHub では #<issue_id>、local では bare ID） |
step_id |
str | 現在のステップ ID |
手動実行（スラッシュコマンド）
$ARGUMENTS = <issue_id>
解決ルール
コンテキスト変数 issue_id が存在すればそちらを使用。
なければ $ARGUMENTS の第1引数を issue_id として使用。
issue_ref はハーネス経由ではプロンプトに自動注入される（prompt.py 側で provider 別に整形）。手動実行時は issue_id から導出する: GitHub 数値 ID なら #<issue_id>、local-* 形式なら bare ID（# を付けない）。
前提知識の読み込み
- docs/dev/docs_maintenance_workflow.md
- docs/dev/workflow_completion_criteria.md
- docs/dev/documentation_update_criteria.md
- docs/dev/shared_skill_rules.md
docs/README.md
実施内容
- worktree と branch を解決する
- docs / workflow / skill 参照の整合を確認する
- links、コマンド例、導線の整合を確認する（
make verify-docs） - Issue 本文の完了条件を照合し、
### ワークフロー完了後の確認項目を除く充足状態を更新する - Issue に最終チェック結果をコメントする
Step 3 詳細: リンク整合性
cd [worktree_dir] && source .venv/bin/activate && make verify-docs
exit 0 必須。verify-docs の検査対象には root AGENTS.md も含まれる。
Step 4 詳細: Issue 本文の完了条件更新
Issue 本文に ## 完了条件 セクション（チェックボックス形式）がある場合:
### ワークフロー完了後の確認項目 は PASS 判定と本文更新の対象外とする。
PASS の場合
同サブセクションより前にある workflow 内完了条件のチェックボックスだけを [x] に更新する。
事後確認のチェックボックスは [ ] のまま維持する。
kaji issue view [issue_id] --json body -q '.body' > /tmp/issue-body.md
# 確認済み条件を [x] に変更
kaji issue edit [issue_id] --commit --body-file /tmp/issue-body.md
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.
- 10d ago First seen · 114 lines · 38 tokens per session scan A 3e7460a04d14
i-doc-final-check is a skill published in the GitHub repository apokamo/kaji (12 stars, last pushed 3d ago), licensed Apache-2.0. It adds 38 tokens to every session and 1,178 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-tech-detailed-methodology
Use when an architect must run the detailed-design portion of technical design, preserve the full lifecycle-stage doctrine for detailed design, and define the concrete runtime, project, flow, data, interface, non-functional, security, recovery, hardware, and implementation-plan surfaces needed for execution.
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…
software-development-norms
Use when writing, reviewing, or refactoring code in any language to apply industrial-grade development norms abstracted from the Alibaba Java Development Handbook. Covers naming, type safety, exceptions, logging, concurrency, databases, project structure, testing, and security with language-agnostic principles and…