create-decision-document

create-decision-document is a skill for Claude Code, Codex from paultyng/skill-issue. It costs 49 tokens per session (437 once invoked), scanned A, original, MIT.

A Notion document creator for recording a decision, its alternatives, their advantages and drawbacks, and the recommended choice.

In plain words
What is it for?
Creating or updating decision, design, evaluation, or comparison documents in a chosen Notion location.
Why use it?
It gives decision discussions a consistent structure, making the reasoning and trade-offs easier to revisit later.

Skill for Claude CodeCodex

Install

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.

agentmods
npx agentmods add skills/paultyng/skill-issue/create-decision-document
Any agent
npx skills add paultyng/skill-issue --skill create-decision-document
Clone the repo
git clone --depth 1 https://github.com/paultyng/skill-issue

Made for: Claude Code, Codex.

Per session 49 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 437 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00049 $0.00437
Opus 5 $0.00024 $0.00218
Sonnet 5 $0.00010 $0.00087
Haiku 4.5 $0.00005 $0.00044

Measured 3d ago against content hash abc6b0d7c2ec, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

create-decision-document 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.

skills/create-decision-document/SKILL.md · 69 lines

What it actually says

Create Decision Document

Create or update a decision document in Notion using the Notion MCP.

1. Gather Context

Determine from the user:

  • Title: what decision is being made
  • Location: which Notion page or database to create under (ask if unclear)
  • Options: the alternatives being evaluated (may emerge during research)

2. Research (if needed)

If the user asks for research before writing:

  • Use Sourcegraph for organization's codebase patterns and precedent
  • Use web search for external APIs, standards, and vendor comparisons
  • Use Notion for existing internal docs and prior decisions
  • Be terse in research summaries

3. Create the Document

Use the Notion MCP to create a page with this structure:

# <Decision Title>

## Problem Statement
<1-2 sentences describing what needs to be decided and why>

## Options

### Option A: <Name>
**Pros**
- <terse bullet>
- <terse bullet>

**Cons**
- <terse bullet>
- <terse bullet>

### Option B: <Name>
**Pros**
- <terse bullet>

**Cons**
- <terse bullet>

## Recommendation
<Which option and why, 1-2 sentences>

Formatting rules:

  • Be terse throughout. No filler.
  • Do not prefix Pros/Cons items with "Good:" or "Bad:".
  • Bullet points, not prose paragraphs.
  • If there are criteria or requirements, use a comparison table rather than repeating them per option.

4. Follow-up

Common follow-up actions (do only if asked):

  • Link a PR to the decision doc
  • Update the recommendation after discussion
  • Add a "Decision" or "Status" field marking the choice as final
Changes

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.

  1. 3d ago First seen · 69 lines · 49 tokens per session scan A abc6b0d7c2ec

Subscribe to this mod's changes

create-decision-document is a skill published in the GitHub repository paultyng/skill-issue (9 stars, last pushed 22d ago), licensed MIT. It adds 49 tokens to every session and 437 once invoked, about $0.0002 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.