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-program-designgit 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-program-design)<a href="https://agentmods.dev/skills/nthnclrk/enablement-skills/enablement-program-design"><img src="https://agentmods.dev/badge/skills/nthnclrk/enablement-skills/enablement-program-design/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-program-design"><img src="https://agentmods.dev/badge/skills/nthnclrk/enablement-skills/enablement-program-design.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.00103 | $0.00989 |
| Opus 5 | $0.00051 | $0.00495 |
| Sonnet 5 | $0.00021 | $0.00198 |
| Haiku 4.5 | $0.00010 | $0.00099 |
Grade A, and why
enablement-program-design 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 9d 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 — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Enablement program design
Design a program that changes observable field behavior and gives managers something to inspect. If it reads like a kickoff deck, rewrite it.
A program is one performance problem, one target behavior, and one inspection. Content calendars, completion dashboards, and "journeys" are not a program.
Program. "AEs will ask one inspectable qualification question before they book SE time. Managers check two calls a week. We stop if inspected calls do not show the question by week 4."
Kickoff. "A four-week enablement journey with kickoff, certification, office hours, and a dashboard of completions."
If a manager cannot tell from a live artifact whether the behavior happened, it is not done.
Confirm Inputs First
Ask only for the inputs that change the design:
- The performance problem, the evidence, and the outcome at risk
- The current behavior, the target behavior, and where it must show up
- Sponsor, accountable owner, and who can approve scope
- Real delivery and manager capacity
- What is already running this quarter
If the problem, owner, audience, or decision authority is unknown, return a discovery brief. Do not invent capacity, baselines, or dates.
Read The Right Reference
Read references/program-charter-template.md for the kickoff-deck tell, diagnosis rules, and the charter shape. Skip it if they already diagnosed the barrier and only want the wrapper filled in.
Default Workflow
- Diagnose the performance problem. Separate evidence from interpretation. Skill and knowledge are not the same as process, product, incentive, capacity, territory, or management. Done when you can name the cause, the confidence, and what remains unknown. If enablement is not a material response, stop and name the owner who should take it.
- Define the target change. Role, workflow moment, current behavior, target behavior, the evidence that it occurred. List what this program will not solve. Done when a manager can inspect the behavior in the workflow, not in a quiz.
- Design the minimum viable program. Match each intervention to a diagnosed barrier. Keep only the assets, practice, manager inspection, and workflow support that produce the target behavior. Cut anything that does not earn its place.
- Set the capacity envelope. Audience volume, facilitator time, manager time, content effort. Reduce scope or sequence cohorts when the plan exceeds capacity. Do not invent hours to make it fit.
- Build the pilot. Cohort, entry, duration, evidence, and the rule to continue, adjust, or stop. Done when week-N evidence can kill the program.
- Establish governance and measurement. Decision rights, approval gates, one primary behavior metric, one primary business outcome. Record definitions, sources, baseline status, and limitations. Do not invent baselines or targets.
- Produce the charter. Make unresolved decisions and next approvals visible. Label it a draft until hard-stop decisions are resolved.
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.
- 9d ago First seen · 76 lines · 103 tokens per session scan A 186448b36ed3
enablement-program-design is a skill published in the GitHub repository nthnclrk/enablement-skills (13 stars, last pushed 19d ago), licensed MIT. It adds 103 tokens to every session and 989 once invoked, about $0.0005 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…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…