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 agentmods add skills/williancesar/saasoned/growth-positioningnpx skills add williancesar/saasoned --skill growth-positioninggit clone --depth 1 https://github.com/williancesar/saasonedWrote 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/williancesar/saasoned/growth-positioning)<a href="https://agentmods.dev/skills/williancesar/saasoned/growth-positioning"><img src="https://agentmods.dev/badge/skills/williancesar/saasoned/growth-positioning.svg" alt="Measured on agentmods" 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 | $0.00106 | $0.01184 |
| Opus 5 | $0.00053 | $0.00592 |
| Sonnet 5 | $0.00021 | $0.00237 |
| Haiku 4.5 | $0.00011 | $0.00118 |
Grade A, and why
growth-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 5d 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 — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Growth: Positioning
Owns "what is this, for whom, in what context." Hub: growth-foundations
(worldview, shared vocabulary, router). Does not redefine hub terms.
Stance. Positioning is a deliberate choice, not destiny (Dunford). Pick one beachhead small enough to dominate (Moore + Zero to One) before any broad-market language. "It's for everyone" is the failure, not the safe option.
Frameworks index
| Framework | Source | Depth |
|---|---|---|
| 5(+1) components + 10-step process + positioning styles | Dunford, Obviously Awesome | references/obviously-awesome.md |
| TALC · the chasm · beachhead/bowling alley · whole product · D-Day · elevator pitch | Moore, Crossing the Chasm | references/crossing-the-chasm.md |
| Niche-monopoly first | Thiel, Zero to One | hub worldview (don't restate) |
| Positioning-rewrite procedure | this skill | references/positioning-rewrite.md |
The positioning-rewrite procedure (default deliverable)
When asked to fix a vague value proposition, run this and output both artifacts:
- Find the lovers. Who already gets disproportionate value? (input to
best-fit customers; if unknown →
growth-customer-discoveryfirst.) - List true competitive alternatives — what the customer would actually do without you (often a spreadsheet, a habit, or nothing — not a rival app).
- Isolate unique attributes alternatives lack.
- Map each attribute → value → proof.
- Name the best-fit customer characteristics that predict who cares most.
- Choose the market category that makes the value obvious (the frame).
- (Optional) layer a trend only if it's real and the customer cares.
- Pick the beachhead (Moore): the single segment to dominate first.
- Emit the Moore elevator pitch (template in crossing-the-chasm.md).
- State the whole product the beachhead needs to fully adopt.
What ships with it
3 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.
- 5d ago First seen · 91 lines · 106 tokens per session scan A 696cc53fe407
growth-positioning is a skill published in the GitHub repository williancesar/saasoned (10 stars, last pushed 3mo ago), licensed MIT. It adds 106 tokens to every session and 1,184 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-31.
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…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
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…