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 nthnclrk/enablement-skills --skill enablement-impact-storygit clone --depth 1 https://github.com/nthnclrk/enablement-skillsWrote 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/nthnclrk/enablement-skills/enablement-impact-story)<a href="https://agentmods.dev/skills/nthnclrk/enablement-skills/enablement-impact-story"><img src="https://agentmods.dev/badge/skills/nthnclrk/enablement-skills/enablement-impact-story/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/nthnclrk/enablement-skills/enablement-impact-story"><img src="https://agentmods.dev/badge/skills/nthnclrk/enablement-skills/enablement-impact-story.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.00081 | $0.00917 |
| Opus 5 | $0.00041 | $0.00458 |
| Sonnet 5 | $0.00016 | $0.00183 |
| Haiku 4.5 | $0.00008 | $0.00092 |
Grade A, and why
enablement-impact-story 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 13d 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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Enablement impact story
Write the strongest story the evidence can carry, then name what you cannot claim yet. If leadership would have to walk the claim back next month, it is not done.
Fails. "The onboarding program delivered 4.2x ROI and caused the 9-point win-rate lift."
Passes. "Day-90 ramp rose 11 points for the Q1 cohort versus the prior two cohorts. Observed result only. We cannot claim causality or ROI: there is no comparison design, and incremental cost is incomplete."
If the user needs the KPI tree or instrumentation, use enablement-metrics-and-instrumentation first.
Confirm Inputs First
Ask only for the inputs that change the claim:
- Initiatives in scope and the decision this memo must support
- Baseline and current values, with population, definition, and period
- Known confounders and any comparison or counterfactual
- For financial ROI only: incremental cost, monetized benefit, time horizon, and the attributable share someone will defend
If financial inputs are incomplete, write an observed-results or contribution story. Do not label it ROI. Do not invent win rates, usage, or ROI.
Read The Right Reference
Read references/impact-story-template.md for claim-mode rules, the ROI method, and worked excerpts. Skip the ROI section unless the user asked for a financial claim and the required inputs are present.
Default Workflow
- Set the evidence boundary. What is measured, for whom, over which comparable periods. Done when every change claim uses one definition, one population, and one pair of windows.
- Choose the claim mode. Observed result, contribution, causal effect, or financial ROI. Pick the least assertive mode that still helps the decision. A pre/post change is an observed result. Do not upgrade it because the narrative would sound better.
- Separate movement from meaning. Show absolute and relative change. Then say what the numbers do and do not support. Put the caveat beside the claim, not in an appendix.
- Build the chain only as far as the evidence goes. Enablement action → behavior change → business outcome. Missing a link means the claim stops at the last supported step.
- Name what you cannot claim yet. Causality, ROI, segment generalization, or a monetized benefit. This section is required. It is the point of the skill.
- Calculate ROI only when the inputs are complete. Attributable benefit, total incremental cost, net benefit, range. Gross revenue or pipeline influenced is not economic benefit. Zero or missing cost blocks the calculation.
- Convert the story into a decision. Continue, adjust, or stop, with options and trade-offs a sponsor can take.
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.
- 13d ago First seen · 72 lines · 81 tokens per session scan A 26baf6953538
enablement-impact-story is a skill published in the GitHub repository nthnclrk/enablement-skills (13 stars, last pushed 23d ago), licensed MIT. It adds 81 tokens to every session and 917 once invoked, about $0.0004 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-30.
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…