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-update/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-update)<a href="https://agentmods.dev/skills/apokamo/kaji/i-doc-update"><img src="https://agentmods.dev/badge/skills/apokamo/kaji/i-doc-update/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-update"><img src="https://agentmods.dev/badge/skills/apokamo/kaji/i-doc-update.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.00047 | $0.01630 |
| Opus 5 | $0.00023 | $0.00815 |
| Sonnet 5 | $0.00009 | $0.00326 |
| Haiku 4.5 | $0.00005 | $0.00163 |
Grade A, and why
i-doc-update 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 — 159 lines — stays where its author put it; the contents beside it link to each section on GitHub.
I Doc Update
ドキュメント修正専用のスキル。 このスキルの目的は ドキュメントのみを更新すること である。コード、設定、テストは変更しない。 ただし、docs の記述が現行実装や運用方針と矛盾していないかは厳格に確認する。
いつ使うか
| タイミング | このスキルを使用 |
|---|---|
| docs-only Issue の主作業 | ✅ 必須 |
| コード変更を伴う Issue | ❌ issue-implement / i-dev-final-check を使用 |
ワークフロー内の位置: review-ready → start → update-doc → review-doc → (fix-doc → verify-doc) → 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/development_workflow.md
- docs/dev/docs_maintenance_workflow.md
- docs/dev/documentation_update_criteria.md
- docs/dev/shared_skill_rules.md
docs/README.mdREADME.md- 変更対象 docs と関連する実装、workflow、設計書、運用ドキュメント
ガードレール
- コード、設定、テストは変更しない
- 事実確認のための read / search / 最小限のコマンド確認は許可
make verify-docsによる全体確認は許可- docs だけでは解決できない不整合を見つけた場合は
ABORT
実行手順
Step 1: Worktree 情報の取得
_shared/worktree-resolve.md の手順に従い、 Worktree の絶対パスを取得すること。以降のステップではこのパスを使用する。
Step 2: 設計書と Issue の確認
- Issue 本文とコメントを確認
- 設計書を確認（docs-only 運用では設計書は任意。存在する場合のみ参照する）:
# 設計書が存在する場合のみ表示。マッチが無くても失敗しない shopt -s nullglob files=([worktree_dir]/draft/design/issue-[issue_id]-*.md) if (( ${#files[@]} > 0 )); then cat "${files[@]}" else echo "[i-doc-update] no draft design file for issue [issue_id] (skipping)" fi - 変更対象 docs と expected outcome を整理
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 · 159 lines · 47 tokens per session scan A b8e61ad72e7e
i-doc-update is a skill published in the GitHub repository apokamo/kaji (12 stars, last pushed yesterday), licensed Apache-2.0. It adds 47 tokens to every session and 1,630 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…