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/danielrmay/claudity/decidenpx skills add danielrmay/claudity --skill decidegit clone --depth 1 https://github.com/danielrmay/claudityWhat 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.00011 | $0.01892 |
| Opus 5 | $0.00005 | $0.00946 |
| Sonnet 5 | $0.00002 | $0.00378 |
| Haiku 4.5 | $0.00001 | $0.00189 |
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 2d 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 — 145 lines — stays where its author put it; the contents beside it link to each section on GitHub.
If there is no protocol directory yet, first scaffold one with python3 "${CLAUDE_PLUGIN_ROOT}/scripts/protocol_init.py" . — decisions are recorded in .clarity-protocol/decisions/. If the user named a decision topic when invoking this skill, work through that decision; follow the guide below from the beginning. A decision is not recorded until the --record-decision script step near the end of this guide has run — writing the decision document and updating the index do not record state.
Decision Guidance
Help the user think through an important decision — one where the choice matters, the tradeoffs are real, and the reasoning should be captured.
Overview
Decisions come up throughout a project — during problem clarification, solution brainstorming, architecture design, failure analysis, or just in conversation. This process isn't a phase in a pipeline; it's a tool you reach for when someone hits a fork that deserves careful thought.
You're already good at helping people think through choices. These instructions remind you what makes a decision well-made and well-documented, not how to analyze tradeoffs (you know how to do that).
When to Use This Process
Use this when:
- A choice has come up that leads to materially different outcomes
- The user asks "should we do X or Y?" and the answer isn't obvious
- You notice a decision being made implicitly that should be made explicitly
- A previous decision needs revisiting because circumstances changed
Don't use this for choices that are straightforward or easily reversible. Not every fork needs a formal process — most don't.
Inputs
Ground your thinking in whatever is relevant from:
.clarity-protocol/goal/problem.md— What the project is trying to achieve.clarity-protocol/goal/stakeholders.md— Whose needs matter.clarity-protocol/goal/requirements.md— What constraints apply.clarity-protocol/solution/solution.md— The current approach.clarity-protocol/solution/architecture.md— Technical context
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.
- 2d ago First seen · 145 lines · 11 tokens per session scan A 2c5a35764f8d
decide is a skill published in the GitHub repository danielrmay/claudity (5 stars, last pushed 2mo ago), licensed MIT. It adds 11 tokens to every session and 1,892 once invoked, about $0.0001 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.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
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…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.