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 drgit 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/dr)<a href="https://agentmods.dev/skills/thkt/dotclaude/dr"><img src="https://agentmods.dev/badge/skills/thkt/dotclaude/dr/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/dr"><img src="https://agentmods.dev/badge/skills/thkt/dotclaude/dr.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.00059 | $0.02051 |
| Opus 5.5 | $0.00024 | $0.00820 |
| Sonnet 5.5 | $0.00012 | $0.00410 |
| Haiku 4.5 | $0.00006 | $0.00205 |
Grade A, and why
dr 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 — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/dr - Decision Record 作成
入力
決定タイトルは $ARGUMENTS で受け取る。空なら AskUserQuestion で New decision/Update existing を確認する。New decision ならタイトルを聞き、Update existing なら <git-root>/docs/decisions/ の既存 DR から選択させる (§ 既存 DR の更新)。新規に作るタイトルは "Adopt X for Y" のような具体的なアクションに整え、5〜64 文字に収めて /:*?"<>| を含めない。保存先は既定で <git-root>/docs/decisions/ で、DR_DIR 環境変数を設定すると変えられる。
${CLAUDE_SKILL_DIR}/../../rules/conventions/DOCUMENTS.md に従い、関連 wiki・DR と原本の適用条件・状態を現在の要求へ照合する。必要な文書更新を今回の合意範囲へ含め、実装と同じ評価へ渡す。
採用ゲート
下表の 3 条件すべてが成り立つときだけプロセスへ進む。欠けるときは DR を作らず、上から順に当てて最初に該当した記録先へ決定を残す。
| 条件 | 欠けたときの記録先 |
|---|---|
| 覆しにくい。後から決定を変えるには相応のコストがかかる | プロジェクトの設計ノート。無ければコミットメッセージ本文 |
| 文脈がないと意外に見える。将来の読み手が「なぜこの形にしたのか」と疑問を持つ | プロジェクトの設計ノート。無ければコミットメッセージ本文 |
| 実在するトレードオフの結果。本物の代替案が存在し、特定の理由で 1 つを選んでいる | コミットメッセージ本文 |
プロセス
| Step | 工程 | 内容 |
|---|---|---|
| 1 | Pre-Check | ${CLAUDE_SKILL_DIR}/scripts/pre-check.ts "$TITLE" を実行する。返り値から使うのは dr_dir と filename (書き込み先)、date (frontmatter)、similar_drs (重複判定) |
| 2 | Type | 決定の意図で決定タイプを判定し、推奨トピックを選ぶ (§ 決定タイプ) |
| 3 | Sources | プロジェクトドキュメント、issue、外部リソースを収集する |
| 4 | Draft | ${CLAUDE_SKILL_DIR}/templates/madr-template.md を dr_dir 配下に filename で写し、収集した内容で埋める (§ YAML Frontmatter) |
| 5 | Challenge | 既存 DR の原則に例外を作る、または既存 DR を supersede する場合だけ /challenge を通し、verdict と成立条件を More Information に 1 行で残す |
| 6 | Validate | ${CLAUDE_SKILL_DIR}/scripts/validate-dr.ts "$DR_FILE" を実行する。exit 0 なら合格。落ちた項目は errors[] に入り、warnings[] は参考 |
| 7 | Index | ${CLAUDE_SKILL_DIR}/scripts/update-index.ts を実行し、dr_dir/README.md を再生成する |
What ships with it
7 files 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 1dee1c552ae9
- 1mo ago Changed fcde3a4aab68
- 1mo ago First seen · 88 lines · 59 tokens per session scan A bbbbc4de8ba2
dr is a skill published in the GitHub repository thkt/dotclaude (12 stars, last pushed 25d ago), licensed MIT. It adds 59 tokens to every session and 2,051 once invoked, about $0.0002 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
team-management-receiving-feedback
How to receive code review as technical evaluation rather than social performance — verify claims against the codebase before implementing, push back with evidence, and drop the performative agreement. Use when responding to a human reviewer, a PR comment, or another AI reviewer, and when deciding whether a suggestion…
review
Adversarial design review of a System Design Doc. Interrogates the staff questions, finds the cost-explosion and failure risks, returns a verdict. Sensors and evals gate.
council
Five independent critic subagents in parallel on an idea, plan, design, R&R strategy, grant, or SKILL.md, then a synthesis pass that ranks findings by how much of the argument rests on them, never by vote count. A markdown work plan gets the plan roster (assumptions, pre-mortem, what to delete, alternatives per piece…
pr-reviewer
Review pull requests with full context. Fetches linked Jira tickets, Figma designs, and Notion docs via MCP, spawns parallel subagents for systematic code review (correctness, security, tests, SOLID, clean code), then drafts friendly, humanized GitHub-ready comments. Use when reviewing PRs, examining code changes, or…
implementation-review
Pre-commit quality gate. Invoke before every git commit, after /flagrare:staleness-audit. Seven checks, plan gaps, use-case coverage gaps, missing test scenarios, test philosophy violations (Kent Dodds Testing Trophy), SOLID violations, Clean Code violations, and security vulnerabilities. Each check is delegated to a…
security-audit
Focused security review of a change. Finds HIGH-CONFIDENCE, concretely exploitable vulnerabilities in the staged diff (injection, broken authn/authz, secrets and data exposure, unsafe deserialization, crypto misuse, SSRF) and audits dependencies when a lockfile moved, using the repo's own package manager. Runs as…