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/thkt/dotclaude/fixnpx skills add thkt/dotclaude --skill fixgit clone --depth 1 https://github.com/thkt/dotclaudeWhat 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.00086 | $0.01668 |
| Opus 5 | $0.00043 | $0.00834 |
| Sonnet 5 | $0.00017 | $0.00334 |
| Haiku 4.5 | $0.00009 | $0.00167 |
Grade A, and why
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 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 — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/fix - クイックバグ修正
入力
$ARGUMENTS の形が入り口を決める。対象は十分に理解できている 1〜3 ファイル規模の問題に限る。audit が返した finding をそのまま渡すときは、複数あれば severity の高い順に 1 件ずつ直す。影響が 4 ファイル以上に及ぶ場合は先に § エスカレーションの複数ファイル判定を確認する。
| パターン | 読み方 | 開始点 |
|---|---|---|
file:line と severity を持つ finding |
そのまま使う | トリアージ |
/^#?[0-9]+$/ |
gh issue view <番号> で本文を読む |
ビルドチェック |
| 空 | AskUserQuestion でバグ説明を尋ねる | アウトカム参照 |
| その他 | バグ説明とみなす | アウトカム参照 |
アウトカム参照
ビルドチェックの前に .claude/OUTCOME.md を読む。不在なら /outcome で stub を生成。バグまたは修正が outcome 状態の中にあるか確認する。範囲外なら § エスカレーション。
ビルドチェック
package.json やプロジェクト設定からビルドコマンドを検出して実行。
| 結果 | 動作 |
|---|---|
| ビルドエラー | Agent(subagent_type: resolver-build) 起動、END |
| エラーなし | トリアージに進む |
トリアージ
Obvious は RCA と regression test 生成の双方を省くため、誤修正リスクの低い finding に限る。
| 入力 | 条件 | パス |
|---|---|---|
| バグ説明 | 単一箇所が特定 + 1〜3 行修正 + 類似パターンなし | Obvious |
| バグ説明 | 断続的、複数の再現条件、または根本原因が不明 | Non-obvious |
| finding | severity low / medium かつ 1〜3 行修正 | Obvious |
| finding | severity critical / high、または修正が非自明 | Non-obvious |
決まりごとの参照
修正するファイルが定まったら、着手の前に python3 ${CLAUDE_SKILL_DIR}/../scribe/scripts/find_wiki_rule.py docs/wiki <バグの語> <触るファイル> --scene implement を実行する。matched のページは今回触るファイルに効く決まりごとなので全て読んでから直す。scenes のページも読む。/think を通らないこの経路にも決まりごとが届くようにするための手順で、plan が無いぶん引くのはこの 1 回きりになる。
Obvious
- 最小限の修正を適用する
- テストを実行し、他のテストに regression がないことを確認する
Non-obvious
RCA の起点は経路で変わる。下表に無い経路はバグ説明から始める。
| 経路 | RCA の扱い |
|---|---|
| finding をそのまま渡した | その file:line と summary を起点として渡す |
| issue 番号を渡し、本文が原因を file:line まで特定している | 省く。その原因を Root cause として引き継ぎ、Pattern だけ判定する |
What ships with it
1 file 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 · 98 lines · 86 tokens per session scan A e6e0203ec00b
fix is a skill published in the GitHub repository thkt/dotclaude (11 stars, last pushed 2d ago), licensed MIT. It adds 86 tokens to every session and 1,668 once invoked, about $0.0004 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
create-modal
Create declarative modals using the modal library API. Covers modal types (confirm, input, select, form), sections (Text, Buttons, Input, Textarea, Checkbox, List, Combo, When, Custom), rendering with OverlayModal, and keyboard/mouse handling. Use when adding modals or dialogs to the application.
merge-strategy
Git merge strategies, conflict resolution approaches, merge vs rebase recommendations, and branch integration patterns in sidecar. Covers pull strategy menu, direct merge workflow, squash merge, commit message templates, configurable defaults, and protected branches. Use when working on git merge features or making…
worktree-switching
Git worktree support in sidecar: worktree detection, switching between worktrees, worktree state management, and plugin reinitialization. Covers the full lifecycle of worktree context switching including registry reinit, per-worktree state persistence, deleted worktree detection and fallback. Use when working on git…
autoprompt
Explicit-only useful-first orchestration. Invoke /autoprompt to turn a mission into one executable roadmap, build dependency-safe lanes, and verify the result with independent reviewers. Never infer invocation from ordinary requests. Never resume from leftover artifacts without an explicit resume instruction.
autoprompt
Explicit-only useful-first orchestration. Invoke /autoprompt to turn a mission into one executable roadmap, build dependency-safe lanes, and verify the result with independent reviewers. Never infer invocation from ordinary requests. Never resume from leftover artifacts without an explicit resume instruction.
openlore-brainstorm
Transform a feature idea into an annotated story using a Domain Sketch or Constrained Option Tree. Use when asked to brainstorm, explore, or shape a feature before implementation.