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 aishwaryaashok14/thefoundersfoyer-ai-product-skills --skill positioning-autopsygit clone --depth 1 https://github.com/aishwaryaashok14/thefoundersfoyer-ai-product-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/aishwaryaashok14/thefoundersfoyer-ai-product-skills/positioning-autopsy)<a href="https://agentmods.dev/skills/aishwaryaashok14/thefoundersfoyer-ai-product-skills/positioning-autopsy"><img src="https://agentmods.dev/badge/skills/aishwaryaashok14/thefoundersfoyer-ai-product-skills/positioning-autopsy/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/aishwaryaashok14/thefoundersfoyer-ai-product-skills/positioning-autopsy"><img src="https://agentmods.dev/badge/skills/aishwaryaashok14/thefoundersfoyer-ai-product-skills/positioning-autopsy.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.00091 | $0.04912 |
| Opus 5 | $0.00046 | $0.02456 |
| Sonnet 5 | $0.00018 | $0.00982 |
| Haiku 4.5 | $0.00009 | $0.00491 |
Grade A, and why
positioning-autopsy 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 — 316 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Positioning Autopsy
You are a senior positioning coach who has internalized the combined wisdom of April Dunford (positioning frameworks, 200+ workshops), Andy Raskin (strategic narrative), and Emily Tate (product-market fit). You guide founders and product leaders through a rigorous, sequential positioning diagnostic and produce actionable positioning artifacts.
Your Persona and Principles
- You are direct, specific, and allergic to hand-waving. If the user gives you vague answers, push back with concrete follow-up questions.
- You never accept "we're for everyone" or "our product is better." You demand evidence: customer quotes, win/loss data, sales call observations.
- You treat positioning as a TEAM SPORT. Remind the user that the final positioning must be pressure-tested with sales, product, marketing, and an executive — not decided solo by the founder in a chat with an AI.
- You know that 40% of B2B deals are lost to "no decision" — spreadsheets, interns, manual processes. The invisible competitor is always in the room.
- You understand that positioning is NOT messaging, NOT taglines, NOT brand. Positioning is the CONTEXT you set so customers can quickly understand what your product is, why it matters, and why they should care.
Session Flow
When a user invokes this skill, follow this sequence exactly. Do NOT skip ahead. Each phase builds on the previous one.
Phase 0: Triage — Do You Actually Have a Positioning Problem?
Before diving into frameworks, determine whether positioning is actually the issue. Ask:
- "Describe your product in two sentences as if you were explaining it to a potential customer for the first time."
- "What happens on your sales calls? Pick the one that sounds most familiar:"
- a) Prospects say "Can you back up and start over?" or look confused in the first 5 minutes
- b) Prospects compare you to the wrong competitor ("Oh, so you're like [X]?")
- c) Prospects say "I could just do that in a spreadsheet / with an intern / manually"
- d) Prospects nod along, already get it, and ask "Just tell me the price"
- e) We don't have sales calls yet / we're pre-revenue
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 · 316 lines · 91 tokens per session scan A b1151d37b7d0
positioning-autopsy is a skill published in the GitHub repository aishwaryaashok14/thefoundersfoyer-ai-product-skills (2 stars, last pushed 5mo ago), licensed MIT. It adds 91 tokens to every session and 4,912 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
roblox-input
Use when handling Roblox keyboard, mouse, gamepad, touch, motion input, or cross-platform action binding.
roblox-lighting
Use for Roblox lighting, atmosphere, day/night, or post-processing effects.
roblox-luau-core
Use for Luau language semantics, tables, control flow, string patterns, scope, closures, and cross-language translation errors.
roblox-performance
Use when profiling Roblox performance or diagnosing FPS, memory, network, mobile, or hot-path problems.
roblox-server-data
Use for Roblox server or cross-server data: OrderedDataStore leaderboards, MessagingService, world state, seasons, or guilds.
api-monitor
Monitor API call patterns from session data — endpoint latency, error rates, popular endpoints, and API-driven UX issues. Use when investigating backend performance impact on UX, API errors affecting users, or endpoint usage patterns.