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/outcomenpx skills add thkt/dotclaude --skill outcomegit 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/outcome)<a href="https://agentmods.dev/skills/thkt/dotclaude/outcome"><img src="https://agentmods.dev/badge/skills/thkt/dotclaude/outcome.svg" alt="Measured on agentmods" 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 | $0.00058 | $0.00684 |
| Opus 5 | $0.00029 | $0.00342 |
| Sonnet 5 | $0.00012 | $0.00137 |
| Haiku 4.5 | $0.00006 | $0.00068 |
Grade A, and why
outcome 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 3d 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.
What it actually says
/outcome - OUTCOME.md 生成 / 更新
他スキルが OUTCOME.md の不在を検知したときの受け皿。停止や警告で返すとアウトカムが空のまま残るので、対話で集めて生成する。
分岐
${CLAUDE_SKILL_DIR}/scripts/validate-outcome.py .claude/OUTCOME.md を実行し、JSON の flow が示すフローへ入る。判定基準はスクリプトが持つ。
| state | 条件 | flow |
|---|---|---|
| absent | ファイル不在 | generate |
| empty | Behavior が空、または TBD のみ | generate |
| ok | Behavior に中身がある | update |
生成
- ${CLAUDE_SKILL_DIR}/templates/outcome.md を読む
- Behavior、Non-goals、Constraints の 3 項目を AskUserQuestion 1 回で各 1 問ずつ収集する。Behavior は 1 つ以上で主体を明示する
- 各 Behavior をアウトカムテストに通す。fail なら書き直してユーザーに再提示する
- テンプレートに流し込み、
.claude/OUTCOME.mdを Write。冒頭文と Indicators はどちらも収集しない。冒頭文を書かず、Indicators はセクションごと落とす - validate-outcome.py を再実行し、
errorsが空になるまで直す。placeholder_leftはプレースホルダの残り、missing_sectionは見出しの欠落
更新
.claude/OUTCOME.mdを読み、現状の各セクションを提示する。生成時に落とした冒頭文と Indicators は、未記入であることを示す- 変更するセクションとその内容を AskUserQuestion で確認する。冒頭文と Indicators を足せるのはこの経路だけ
- 変更後の Behavior をアウトカムテストに通してから Edit する
- validate-outcome.py を再実行し、
errorsが空であることを確認する warningsにmissing_indicatorがあれば、その指標を足すかをユーザーに確認する。Indicators セクションを持ちながら Time/Error rate/Value のどれかを欠く状態を指す
What ships with it
2 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.
- 3d ago First seen · 38 lines · 58 tokens per session scan A aff124f8223a
outcome is a skill published in the GitHub repository thkt/dotclaude (12 stars, last pushed yesterday), licensed MIT. It adds 58 tokens to every session and 684 once invoked, about $0.0003 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…
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.
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.
ap-feature-coordinator
L1 feature coordinator - drives approved ROADMAP.md lanes through their required build/review/verification gates and owns the run-wide feature frontier.