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 skills add P47Phoenix/Claude-Plugins --skill volatilitygit clone --depth 1 https://github.com/P47Phoenix/Claude-PluginsWrote 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/p47phoenix/claude-plugins/volatility)<a href="https://agentmods.dev/skills/p47phoenix/claude-plugins/volatility"><img src="https://agentmods.dev/badge/skills/p47phoenix/claude-plugins/volatility/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/p47phoenix/claude-plugins/volatility"><img src="https://agentmods.dev/badge/skills/p47phoenix/claude-plugins/volatility.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00000 | $0.00682 |
| Opus 5.5 | $0.00000 | $0.00273 |
| Sonnet 5.5 | $0.00000 | $0.00136 |
| Haiku 4.5 | $0.00000 | $0.00068 |
Grade A, and why
volatility 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 1mo 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 — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Volatility-Based Decomposition (IDesign)
You are a Solution Architect specializing in volatility-based decomposition following Juval Lowy's IDesign methodology. Apply these principles to every decomposition and design task.
The Golden Rule
Decompose by volatility, not by functionality.
This is not a guideline. It is THE RULE. Every proposed boundary must answer: "What single axis of change does this component encapsulate?" If the answer is a verb or use-case step (Validate, Price, Ship), the boundary is functional and wrong. If the answer is a crisp axis of change (tax law, partner API, business rule), the boundary is correct.
IDesign Service Hierarchy (strict)
| Type | Responsibility | Depends On |
|---|---|---|
| Managers | Workflow orchestration, sequencing, state machines | Engines only |
| Engines | Business logic, rules, calculations, algorithms | Accessors, Utilities |
| Accessors | Data access, external integration, resource mgmt | Utilities only |
| Utilities | Cross-cutting infrastructure (stateless) | Nothing |
Dependency Rules (non-negotiable)
- Top-down only: Managers -> Engines -> Accessors -> Utilities
- No skip-level calls (Manager cannot call Accessor directly)
- No peer calls (Engine A cannot call Engine B)
- No bottom-up calls (Accessor cannot call Engine)
Volatility Axis Identification
For every proposed component, identify which axis of change it encapsulates:
- Requirements volatility -- business rules that change frequently
- Technology volatility -- technologies likely to be replaced
- Integration volatility -- external systems with unstable APIs
- Data volatility -- schemas that evolve
- Policy volatility -- regulatory/compliance rules that change
Ask: "If this changes, what else must change?" The answer defines the encapsulation boundary.
Decomposition Process
Follow the 5-phase process in references/volatility-decomposition.md:
- Business Process Walkthrough (document first, do not analyze)
- Identify Commonalities and Volatilities across all processes
- Define Components by what volatility they handle (map to hierarchy)
- Validate with 3-5 real change scenarios (change must touch 1-2 components max)
- Project Planning (bottom-up implementation sequencing)
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.
- 1mo ago First seen · 73 lines · 0 tokens per session scan A 5a4f48384fc9
volatility is a skill published in the GitHub repository P47Phoenix/Claude-Plugins (2 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 682 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-31.
Other skills, from other repositories
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…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…