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 value-prop-and-positioninggit 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/value-prop-and-positioning)<a href="https://agentmods.dev/skills/nthnclrk/enablement-skills/value-prop-and-positioning"><img src="https://agentmods.dev/badge/skills/nthnclrk/enablement-skills/value-prop-and-positioning/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/value-prop-and-positioning"><img src="https://agentmods.dev/badge/skills/nthnclrk/enablement-skills/value-prop-and-positioning.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.00060 | $0.00713 |
| Opus 5 | $0.00030 | $0.00357 |
| Sonnet 5 | $0.00012 | $0.00143 |
| Haiku 4.5 | $0.00006 | $0.00071 |
Grade A, and why
value-prop-and-positioning 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 11d 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 — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Value prop and positioning
Positioning is decision support against the buyer's real alternative. If it reads like a slogan, rewrite it.
The alternative that matters most is often no change: the spreadsheet, the manual workaround, the in-house tool they already paid for.
Alternative. "Ops VPs keep the spreadsheet because it is already in the Friday review. We win when missed handoffs have a named cost and a named owner. We lose when the pain is 'it would be nicer to have a system.'"
Slogan. "The AI-powered platform of record for modern operations teams."
If you cannot name what the buyer would do instead, you do not have positioning yet.
Confirm Inputs First
Ask only for what changes the thesis:
- Who is buying, and what job they are trying to finish
- What they use or consider instead, including no change
- The capability that is actually different, and how it produces an outcome
- Approved proof and claim limits
Do not turn an unverified hypothesis into an external outcome claim.
Read The Right Reference
Read references/positioning-canvas.md for thesis modes, the alternatives map, and the differentiation chain. Skip it if the user already has a canvas and only wants a rewrite.
Default Workflow
- Name the buyer task. Trigger, progress sought, current approach, decision criteria, cost of staying put. Done when you can say why this is a decision, not a feature launch.
- Map real alternatives. Only options there is evidence for. Include no change. Do not invent a competitor set to fill a table.
- Build the differentiation chain. Capability, mechanism, buyer outcome, proof. Drop claims that are only different in wording. "AI-powered" and "easy" are not chains.
- Choose a thesis mode. Evidence-backed, product-demonstrable without an outcome claim, or internal hypothesis with no external use. Write only the pillars that mode can support.
- Translate by decision role. Change the task, criterion, outcome, proof, and risk, not just the vocabulary.
- Add why-now only when a real trigger, cost of delay, or decision window exists.
- State who this is not for, and which claims you cannot support.
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.
- 11d ago First seen · 69 lines · 60 tokens per session scan A 425aa549e329
value-prop-and-positioning is a skill published in the GitHub repository nthnclrk/enablement-skills (13 stars, last pushed 22d ago), licensed MIT. It adds 60 tokens to every session and 713 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…