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/ozzy-labs/suasor/plan-draftnpx skills add ozzy-labs/suasor --skill plan-draftgit clone --depth 1 https://github.com/ozzy-labs/suasorWrote 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/ozzy-labs/suasor/plan-draft)<a href="https://agentmods.dev/skills/ozzy-labs/suasor/plan-draft"><img src="https://agentmods.dev/badge/skills/ozzy-labs/suasor/plan-draft.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.00151 | $0.01031 |
| Opus 5 | $0.00076 | $0.00515 |
| Sonnet 5 | $0.00030 | $0.00206 |
| Haiku 4.5 | $0.00015 | $0.00103 |
Grade A, and why
plan-draft 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 4d 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
plan-draft
起点（issue / 設計メモ / source）を「計画」に落とす HITL write skill。「計画する」動詞を担い、文脈を集めて task / decision 候補に分解し、承認分のみ保存する（ADR-0004）。next-actions（既存 task の列挙）に対し、本 skill は新しい計画の生成・分解側。
いつ発火するか
- 「これを分解して」「タスクに分解」「この issue を計画化」
- 「設計のたたき台」「進め方を考えて」「計画に落として」
何をするか（MCP tool flow）
read で文脈を集め、計画本文は text-only、task/decision 化は HITL（ADR-0004）。
- 起点の文脈を集める:
source.get（対象 issue/メモの本文）/search（mode=semantic）・search（関連やりとり）/graph.related（関連 decision・先行仕様）。広く調べるならfindskill を併用 - 分解方針・マイルストーン・順序/依存の計画ドラフト本文を host LLM が構成して返す（text-only・persist しない。draft / draft と同じ作法）
- 計画中の実行項目を
propose.generate（mode=source_extract）で task / decision 候補に分解する（source_extractの許可 kind =task/decision/reply_draft） propose.list（state=pending）で候補を提示し、ユーザー確認を取る- 承認分のみ
propose.applyで保存（idempotent）。不要な候補はpropose.reject（任意で理由）
制約
- HITL。人の承認なしに
propose.applyを呼ばない。auto-apply しない。計画ドラフト本文は persist しない - task 間の順序/依存は当面計画本文のサマリで提示し、task 自体は個別に作成する（順序メタを持つ専用
planmode は将来拡張・別 issue） - 既存 task の状態確認/列挙は
next-actions、完了遷移はtask-updateを使う - 計画ドラフト本文をファイルで欲しい場合は
draft.export（HITL write）で.md/.txtにローカル書き出しできる（送信はしない・ADR-0025） - 本 skill は手順書のみで実処理を持たない
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.
- 4d ago First seen · 52 lines · 151 tokens per session scan A 9050fe33385e
plan-draft is a skill published in the GitHub repository ozzy-labs/suasor (0 stars, last pushed 25d ago), licensed MIT. It adds 151 tokens to every session and 1,031 once invoked, about $0.0008 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…