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 commands/ccplugins/awesome-claude-code-plugins/decidegit clone --depth 1 https://github.com/ccplugins/awesome-claude-code-pluginsWhat 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.00000 | $0.00649 |
| Opus 5 | $0.00000 | $0.00324 |
| Sonnet 5 | $0.00000 | $0.00130 |
| Haiku 4.5 | $0.00000 | $0.00065 |
Grade A, and why
decide 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 yesterday.
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 — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/decide - Technical Decision Gate
Forces structured decision-making and creates an auditable Agent Decision Record (AgDR).
Trigger
/decide "what you're deciding"
/decide which state management library to use
/decide how to implement caching
Process
1. Parse Decision Topic
Extract the decision topic from input. If unclear, ask:
What technical decision do you need to make?
2. Gather Context
Identify decision-relevant context only:
- What problem are we solving?
- What constraints exist?
- What's already in the codebase?
3. List Options
Present 2-4 options in a table:
| Option | Pros | Cons |
|--------|------|------|
| Option A | ... | ... |
| Option B | ... | ... |
4. Make Decision
State the chosen option with justification.
5. Generate AgDR
Create file at {project-root}/docs/agdr/AgDR-{NNNN}-{slug}.md:
---
id: AgDR-{NNNN}
timestamp: {ISO-8601: YYYY-MM-DDTHH:MM:SSZ}
agent: claude-code
model: {model-id from environment}
session: {session-id if available}
trigger: user-prompt
status: executed
---
# {short title}
> In the context of {context}, facing {concern}, I decided {decision} to achieve {goal}, accepting {tradeoff}.
## Context
{Decision-relevant context only - 2-4 bullets}
## Options Considered
| Option | Pros | Cons |
|--------|------|------|
| ... | ... | ... |
## Decision
Chosen: **{option}**, because {justification}.
## Consequences
- {consequence 1}
- {consequence 2}
## Artifacts
- {commit/PR links when available}
6. Get Next ID
# Find highest existing AgDR number
ls docs/agdr/AgDR-*.md 2>/dev/null | sort -V | tail -1 | grep -oP 'AgDR-\K\d+'
# Increment by 1, or start at 0001
7. Return Decision
Output the decision so work can continue:
Decision: {chosen option}
AgDR-{NNNN} created at docs/agdr/AgDR-{NNNN}-{slug}.md
Proceeding with: {brief action}
Rules
- Always create AgDR - No decision without a record
- Context is minimal - Only what influenced the decision
- Y-statement required - One-line summary at top
- Options table required - At least 2 options compared
- Justification required - "because" clause mandatory
- Timestamp precise - Full ISO-8601 with time
- Slug from title - Lowercase, hyphens, max 50 chars
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.
- yesterday First seen · 111 lines · 0 tokens per session scan A 86929a889ea4
decide is a command published in the GitHub repository ccplugins/awesome-claude-code-plugins (926 stars, last pushed 19d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 649 tokens. 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 commands, from other repositories
e2e-test-command
This is a mock slash command file for E2E testing.
atl-fetch-confluence
Command "atl-fetch-confluence" from lc-semba-ryuichiro/semba-claude-plugins, covering confluence 情報取得コマンド, コマンド実行, オプション, 実行例 and ページ情報を取得（json）.
atl-fetch-jira
Command "atl-fetch-jira" from lc-semba-ryuichiro/semba-claude-plugins, covering jira 情報取得コマンド, コマンド実行, オプション, 実行例 and 課題情報を取得（json）.
webpify-list
WebPファイルの一覧と情報を表示.
webpify
画像ファイルを WebP 形式に変換.
diagram-drawio
Command "diagram-drawio" from lc-semba-ryuichiro/semba-claude-plugins, covering draw\.io図作成コマンド, 実行手順, スキル参照（必須） and 出力オプション.