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 quarterly-enablement-plannergit 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/quarterly-enablement-planner)<a href="https://agentmods.dev/skills/nthnclrk/enablement-skills/quarterly-enablement-planner"><img src="https://agentmods.dev/badge/skills/nthnclrk/enablement-skills/quarterly-enablement-planner/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/quarterly-enablement-planner"><img src="https://agentmods.dev/badge/skills/nthnclrk/enablement-skills/quarterly-enablement-planner.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.00079 | $0.00923 |
| Opus 5 | $0.00039 | $0.00462 |
| Sonnet 5 | $0.00016 | $0.00185 |
| Haiku 4.5 | $0.00008 | $0.00092 |
Grade A, and why
quarterly-enablement-planner 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 12d 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.
Quarterly enablement planner
Build a quarter plan that names what will not happen. If everything is a priority, it is not a plan.
A quarter plan is a capacity-backed stack: what ships, what waits, and the trade-off that made that true. Initiative charters belong in enablement-program-design.
Plan. "This quarter we ship the packaging launch and the AE qualification program. Partner certification, the battlecard refresh, and the new-hire rewrite wait. Capacity is 18 delivery days; those three do not fit."
Wish list. "Twelve initiatives across launch, onboarding, coaching, and content, all marked P1, owners TBD."
If you cannot name what will not happen, who decided, and what would put it back, it is not done.
Confirm Inputs First
Ask only for the inputs that change the stack:
- The quarter and the business priorities
- Immovable launches, compliance dates, and peak selling periods
- Gross capacity by constrained owner, plus BAU, carryover, and leave
- Candidate work with evidence, dependencies, and required effort
If owner capacity is unknown, leave that work unscheduled. Do not invent capacity, fixed dates, or commitments to make the roadmap fit.
Read The Right Reference
Read references/quarterly-plan-template.md for the defer test, scoring anchors, and the must-do conflict rule. Skip it if they already scored the stack and only want the calendar written.
Default Workflow
- Set the planning boundary. Quarter, priorities, immovable dates, and the roles covered. Done when you know which decisions this plan must protect.
- Build the net-capacity ledger first.
Net = Gross - BAU - carryover - leave - protected contingency. Use the contingency they supplied; do not invent a percentage. Include design, SME, delivery, reinforcement, and measurement. Done when every constrained owner has a number in one unit. - Score the candidates. Impact and necessity from the reference anchors. Rate confidence and effort separately. Do not divide priority by effort.
- Classify each item.
must do,should do,validate, ordefer. Must-do still needs an owner and a capacity plan. Done when every candidate has one label and a reason. - Name what will not happen this quarter. Defer list with rationale, re-entry condition, and decision owner. If must-do load exceeds capacity, surface the conflict: cut scope, move a date with the authorized owner, add verified capacity, or displace something else. Do not silently overbook.
- Sequence what will happen. Real decision dates, dependencies, peak selling, and field absorption. Overlapping launches can exceed audience capacity even when enablement has time. Assign owners, milestones, and due dates only when they are known.
- Set review points. Decision gates, material dependency dates, and explicit re-plan triggers. New work enters through a trade-off: consume contingency, reduce scope, or displace an item.
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.
- 12d ago First seen · 73 lines · 79 tokens per session scan A 07b51c06252b
quarterly-enablement-planner is a skill published in the GitHub repository nthnclrk/enablement-skills (13 stars, last pushed 23d ago), licensed MIT. It adds 79 tokens to every session and 923 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…