kaji: Skill for Claude Code

.claude/skills/i-doc-fix/SKILL.md

i-doc-fix is a skill for Claude Code from apokamo/kaji. It costs 33 tokens per session (730 once invoked), scanned A, original, Apache-2.0.

A documentation-only repair skill for addressing issues found during a documentation review. It follows a review-and-verify workflow and does not change application code, settings, or tests.

In plain words
What is it for?
It is for fixing documentation issues, checking links and consistency, and preparing documentation-only changes for review.
Why use it?
It helps resolve documented review findings while keeping the scope limited to the affected documentation.

Skill for Claude Code

Written for Claude Code: $ARGUMENTS substitution. Also seen: mentions CLAUDE.md; mentions AGENTS.md.

This is apokamo/kaji's own configuration. It tells Claude Code how to work on kaji itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything kaji configures →

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is cd [worktree_dir] && python3 scripts/check_doc_links.py [changed-markdown-files...].

Reuse

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.

Copy the file
curl -O https://raw.githubusercontent.com/apokamo/kaji/main/.claude/skills/i-doc-fix/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/apokamo/kaji

Made for: Claude Code.

Wrote 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.

agentmods badge for i-doc-fix

README.md
[![agentmods](https://agentmods.dev/badge/skills/apokamo/kaji/i-doc-fix/github.svg)](https://agentmods.dev/skills/apokamo/kaji/i-doc-fix)
Your own site
<a href="https://agentmods.dev/skills/apokamo/kaji/i-doc-fix"><img src="https://agentmods.dev/badge/skills/apokamo/kaji/i-doc-fix/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.

agentmods 80×15 button for i-doc-fix

Your own site · 80×15
<a href="https://agentmods.dev/skills/apokamo/kaji/i-doc-fix"><img src="https://agentmods.dev/badge/skills/apokamo/kaji/i-doc-fix.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 33 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 730 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00033 $0.00730
Opus 5 $0.00016 $0.00365
Sonnet 5 $0.00007 $0.00146
Haiku 4.5 $0.00003 $0.00073

Measured 9d ago against content hash 726d24136f1d, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

i-doc-fix 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.

.claude/skills/i-doc-fix/SKILL.md · 79 lines

What it actually says

I Doc Fix

docs review の指摘事項に対応する。このスキルでも コード、設定、テストは変更しない

いつ使うか

タイミング このスキルを使用
i-doc-review または i-doc-verify が RETRY のとき ✅ 必須

ワークフロー内の位置: update-doc → review-doc → fix-doc → verify-doc

入力

ハーネス経由(コンテキスト変数)

変数 説明
issue_id str 正規化済み Issue ID(GitHub 数値または local ID)
issue_ref str 人間可読の Issue 参照(GitHub では #<issue_id>、local では bare ID)
step_id str 現在のステップ ID
previous_verdict str 前ステップの verdict

手動実行(スラッシュコマンド)

$ARGUMENTS = <issue_id>

解決ルール

コンテキスト変数 issue_id が存在すればそちらを使用。 なければ $ARGUMENTS の第1引数を issue_id として使用。

issue_ref はハーネス経由ではプロンプトに自動注入される(prompt.py 側で provider 別に整形)。手動実行時は issue_id から導出する: GitHub 数値 ID なら #<issue_id>local-* 形式なら bare ID(# を付けない)。

前提知識の読み込み

  1. docs/dev/documentation_update_criteria.md
  2. docs/dev/shared_skill_rules.md

実行手順

  1. previous_verdict または Issue コメントから最新レビュー結果を取得
  2. Must Fix を 1 件ずつ検討
  3. docs のみ修正
  4. 実装 / CLI / AGENTS.md / CLAUDE.md / 関連 docs との整合を再確認
  5. 修正対象ファイルに絞って以下を実行:
    cd [worktree_dir] && python3 scripts/check_doc_links.py [changed-markdown-files...]
    
  6. docs のみコミット
  7. 対応内容を Issue にコメント

Verdict 出力

---VERDICT---
status: PASS
reason: |
  docs review の指摘に対応した
evidence: |
  Must Fix 項目を修正し、関連する docs と実装の整合を再確認した
suggestion: |
---END_VERDICT---

status の選択基準

status 条件
PASS 修正完了
ABORT docs 修正だけでは解決不能
Changes

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.

  1. 9d ago First seen · 79 lines · 33 tokens per session scan A 726d24136f1d

Subscribe to this mod's changes

i-doc-fix is a skill published in the GitHub repository apokamo/kaji (12 stars, last pushed 2d ago), licensed Apache-2.0. It adds 33 tokens to every session and 730 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.

Related

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.

xiaohei-info/oh-my-multica · 65 tokens

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.

xiaohei-info/oh-my-multica · 57 tokens

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.

xiaohei-info/oh-my-multica · 49 tokens

creative-claude-design

Design one-off HTML artifacts (landing, deck, prototype).

xiaohei-info/oh-my-multica · 18 tokens

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…

xiaohei-info/oh-my-multica · 120 tokens

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…

xiaohei-info/oh-my-multica · 66 tokens