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-house-stylegit 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-house-style)<a href="https://agentmods.dev/skills/nthnclrk/enablement-skills/enablement-house-style"><img src="https://agentmods.dev/badge/skills/nthnclrk/enablement-skills/enablement-house-style/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-house-style"><img src="https://agentmods.dev/badge/skills/nthnclrk/enablement-skills/enablement-house-style.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.00066 | $0.00334 |
| Opus 5 | $0.00033 | $0.00167 |
| Sonnet 5 | $0.00013 | $0.00067 |
| Haiku 4.5 | $0.00007 | $0.00033 |
Grade A, and why
enablement-house-style 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.
What it actually says
Enablement house style
Shared rules. Not a deliverable.
These rules apply to every skill in this pack. Load this file when a specialist skill is silent on context, evidence, or writes. Do not use for a talk track, battlecard, or other specialist deliverable.
Fails. Inventing a customer logo so a talk track lands.
Passes. A proof slot marked needs source.
When this applies
Any enablement skill in this pack. Skip it for a clear specialist ask unless safety is the question.
Rules
- Use current user context or
.enablement/context.mdwhen it is fresh. Never edit shared context unless the user asked and confirmed a preview. - Ask only for inputs that change this output.
- Do not invent proof, pricing, security, customers, win rates, or ROI.
- Label assumptions. Keep facts, inferences, and conflicts distinct.
- Do not write to CRM, email, Slack, or a CMS without an explicit yes.
- Internal-only material stays internal.
The test
Would a tired enablement lead trust this on Tuesday? If not, rewrite it.
Done when a specialist skill can run without restating these rules, and the output would survive a skeptical manager.
What ships with it
1 file 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 · 34 lines · 66 tokens per session scan A c11ea59ed143
enablement-house-style is a skill published in the GitHub repository nthnclrk/enablement-skills (13 stars, last pushed 22d ago), licensed MIT. It adds 66 tokens to every session and 334 once invoked, about $0.0003 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…