positioning-map

positioning-map is a skill for Claude Code from anysiteio/agent-skills. It costs 201 tokens per session (7,419 once invoked), scanned A, original, MIT.

A method for comparing three to five competitors across several meaningful signals and finding an unclaimed position. Positioning describes which customers a product serves and how it differs from alternatives.

In plain words
What is it for?
Use it to compare competitors' messaging, prices, products, customers, and hiring, then choose among possible market positions.
Why use it?
It turns a vague competitive discussion into a structured comparison and helps identify choices the founder could make.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: positional $N argument; mentions Claude Code.

Part of the anysite-skills plugin — 33 skills shipped together

Install

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.

agentmods
npx agentmods add skills/anysiteio/agent-skills/positioning-map
Any agent
npx skills add anysiteio/agent-skills --skill positioning-map
Clone the repo
git clone --depth 1 https://github.com/anysiteio/agent-skills

Made for: Claude Code.

Or install anysite-skills, the plugin that ships this one along with the rest of its 33 skills.

Wrote 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.

agentmods badge for positioning-map

README.md
[![agentmods](https://agentmods.dev/badge/skills/anysiteio/agent-skills/positioning-map.svg)](https://agentmods.dev/skills/anysiteio/agent-skills/positioning-map)
Your own site
<a href="https://agentmods.dev/skills/anysiteio/agent-skills/positioning-map"><img src="https://agentmods.dev/badge/skills/anysiteio/agent-skills/positioning-map.svg" alt="Measured on agentmods" height="20"></a>
Per session 201 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 7,419 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00201 $0.07419
Opus 5 $0.00101 $0.03710
Sonnet 5 $0.00040 $0.01484
Haiku 4.5 $0.00020 $0.00742

Measured 6d ago against content hash 44ba48534bed, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

positioning-map 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 6d 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.

skills/positioning-map/SKILL.md · 315 lines

How it starts

The opening of the file, as written. The whole thing — 315 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Positioning Map

Positioning isn't marketing copy — it's a product decision about who you say no to. This skill makes that choice visible by mapping competitors on 5 signal axes, locating the empty space, and forcing you to pick between 3 candidate moves rather than defaulting to the first one that sounds good.

Founders consistently underweight four things on competitor positioning: hero copy is the most-curated surface (so trust it least), pricing reveals who they actually sell to, what they ship reveals what they think matters, and who they hire reveals where they're going next quarter (the leakiest signal of all). Customer logos reveal who they actually catch, which often contradicts who they pitch.

Frameworks this skill draws from

This skill is the operational version of three positioning frameworks, executed against real public data:

  1. April Dunford — Obviously Awesome (5 components): competitive alternatives, unique attributes, value (and proof), target market characteristics, market category. Dunford's #1 insight: start with competitive alternatives, not with what you do. This skill operationalizes that by always grounding "the empty quadrant" against the actual competitor set, not against an abstract market.
  2. Geoffrey Moore — Crossing the Chasm (positioning statement template): "For [target customer] who [need], the [product] is a [category] that [benefit]. Unlike [primary alternative], our product [primary differentiation]." This is the format of the deliverable — the one-sentence positioning move.
  3. Ries & Trout — Positioning: The Battle for Your Mind (mental real-estate): you can only own ONE word/concept in the customer's mind. The "empty quadrant" framing inherits from this: the position you can own is the one nobody else is claiming AND that customers care about.

Adjacent frameworks worth knowing but not directly encoded here: Treacy & Wiersema's three value disciplines (product leadership / operational excellence / customer intimacy — pick one, do the others adequately) and Ulwick's outcome-driven JTBD (positioning aligned to unmet desired outcomes). If the founder uses these in their own thinking, fold them into the axis choices.

Read the full file on GitHub · 315 lines

Changes

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.

  1. 6d ago First seen · 315 lines · 201 tokens per session scan A 44ba48534bed

Subscribe to this mod's changes

positioning-map is a skill published in the GitHub repository anysiteio/agent-skills (19 stars, last pushed 21d ago), licensed MIT. It adds 201 tokens to every session and 7,419 once invoked, about $0.0010 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.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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…

microsoft/ai-agents-for-beginners · 200 tokens

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…

microsoft/vscode · 72 tokens

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.

microsoft/vscode · 53 tokens

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…

microsoft/vscode · 71 tokens

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…

vercel/next.js · 95 tokens