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 skills add thkt/dotclaude --skill fixgit clone --depth 1 https://github.com/thkt/dotclaudeWrote 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/thkt/dotclaude/fix)<a href="https://agentmods.dev/skills/thkt/dotclaude/fix"><img src="https://agentmods.dev/badge/skills/thkt/dotclaude/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.
<a href="https://agentmods.dev/skills/thkt/dotclaude/fix"><img src="https://agentmods.dev/badge/skills/thkt/dotclaude/fix.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00086 | $0.01862 |
| Opus 5.5 | $0.00034 | $0.00745 |
| Sonnet 5.5 | $0.00017 | $0.00372 |
| Haiku 4.5 | $0.00009 | $0.00186 |
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 1mo 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 — 104 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 |
決まりごとの参照
${CLAUDE_SKILL_DIR}/../../rules/conventions/DOCUMENTS.md に従い、関連 wiki・DR と原本の適用条件・状態を現在の要求へ照合する。必要な文書更新を今回の合意範囲へ含め、実装と同じ評価へ渡す。
修正するファイルが定まったら、着手の前に ${CLAUDE_SKILL_DIR}/../scribe/scripts/find_wiki_rule.ts docs/wiki <バグの語> <触るファイル> --scene implement を実行する。matched のページは今回触るファイルに効く決まりごとなので全て読んでから直す。scenes のページも読む。/think を通らないこの経路にも決まりごとが届くようにするための手順で、plan が無いぶん引くのはこの 1 回きりになる。
Obvious
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.
- 1mo ago Changed · +6 lines 30727c503b4c
- 1mo ago Changed f8b67016d831
- 1mo ago First seen · 98 lines · 86 tokens per session scan A e6e0203ec00b
fix is a skill published in the GitHub repository thkt/dotclaude (12 stars, last pushed 25d ago), licensed MIT. It adds 86 tokens to every session and 1,862 once invoked, about $0.0003 per session on Opus 5.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
simplify-code
Parallel 4-agent cleanup of recent code changes.
skill-creator
Create new skills (SKILL.md files), modify and improve existing skills, and design skill descriptions for accurate triggering. Use when the user wants to create a new skill from scratch, edit an existing skill, optimize a skill's description, or convert a workflow they just demonstrated into a reusable skill.
next-action
Use when the user wants a next-action recommendation based on current state — reads handoff/git/lessons/STATE and proposes top-3 by impact. Trigger: '/next', 'what should I do next', 'next action'. Proposes only, never executes.
insights
Use when the user types /weekly or /monthly, asks for a weekly or monthly journal review or retrospective, asks 'how was my week' or 'how was my month', or wants trends, anomalies, or patterns across recent journal entries. Also fires when regenerating an insight report for a past week or month. NOT for writing…
ai-architect-review
Review the architecture of a system that calls a language model. Use when adding an agent loop, a retrieval path, a tool surface, or an MCP server to a codebase; when a system that worked in a demo is being prepared for production; or when asked to audit, review, or plan AI/agent architecture. Checks the four…
patterns
Use when the user says /patterns or mentions the Instinct Engine, says "I keep noticing" or "this keeps coming up", after a weekly review, when a pattern is hardening, or at session end after repeated corrections, 5+ tool-call friction on a routine task, dead-end backtracking, or an undocumented discovery. Also as a…