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 sanky369/vibe-building-skills --skill positioning-anglesgit clone --depth 1 https://github.com/sanky369/vibe-building-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/sanky369/vibe-building-skills/positioning-angles)<a href="https://agentmods.dev/skills/sanky369/vibe-building-skills/positioning-angles"><img src="https://agentmods.dev/badge/skills/sanky369/vibe-building-skills/positioning-angles/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/sanky369/vibe-building-skills/positioning-angles"><img src="https://agentmods.dev/badge/skills/sanky369/vibe-building-skills/positioning-angles.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.00152 | $0.02058 |
| Opus 5 | $0.00076 | $0.01029 |
| Sonnet 5 | $0.00030 | $0.00412 |
| Haiku 4.5 | $0.00015 | $0.00206 |
Grade A, and why
positioning-angles 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 — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Positioning Angles
Produce a positioning statement the rest of the marketing system can repeat: one claim, built from the market's stage, the offer's unique mechanism, and a single psychological angle. Governing principle: positioning is not being better, it's being different in a way the audience cares about — and one angle typically outperforms the others by a wide margin, so commit to one and treat it as a bet to test, not a truth.
When to use / when not to
- Use whenever a core claim is missing, weak, or generic — before landing pages, content strategy, or email work.
- If the user is unsure the product itself is differentiated (not just the message), hand off to
skills/product-strategy/foundation-sprint— it pressure-tests the underlying bet with a differentiation 2x2; come back here to turn its output into market-facing language. - If the claim exists and the user needs it written into a page, use
skills/marketing/direct-response-copy. - Audit mode: user has positioning but doubts it → skip to Step 4 and run the three tests against it; fix the failing part using the matching step.
Intake
One batch; skip anything already known from context or from skills/marketing/orchestrator:
- What do you sell, in one sentence, and to whom?
- What are the 2–3 alternatives your customer actually compares you to (including "do nothing" or a spreadsheet)?
- What do you do differently from those alternatives — any step, ingredient, or approach they skip?
- How saturated is your market: do you have to explain the category, or is the buyer already drowning in options and skeptical claims?
Don't stall: if the product and market are recognizable, infer stage and competitors, state assumptions, and proceed.
Workflow
1. Diagnose the market stage
The market's maturity dictates the message form. Classify using the signals, then adopt that stage's approach:
| Stage | Signal (how to identify) | Approach | Template |
|---|---|---|---|
| NEW | You must explain what the category is | Simple promise | "Now you can [X]" |
| GROWING | Competitors exist but aren't saturating ads/content | Bigger claim | "[X] in [specific time]" |
| CROWDED | Multiple well-known players, active advertising | Show mechanism | "The [method] that works" |
| JADED | Buyers say "all [X] are scams"; category has burned people | Prove it | "[Data/proof] that shows [X]" |
| MATURE | Clear leaders; buyers identify with brands | Sell identity | "For [people who are X]" |
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 · 121 lines · 152 tokens per session scan A cfe6853e2a89
positioning-angles is a skill published in the GitHub repository sanky369/vibe-building-skills (30 stars, last pushed 2mo ago), licensed MIT. It adds 152 tokens to every session and 2,058 once invoked, about $0.0008 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
dep-auditor
A read-only audit of a project’s third-party packages for known security issues, version health, and license facts. It uses the versions actually selected by lockfiles, which record the exact packages installed, rather than relying only on version ranges.
skill-curator
A Chinese-language evaluator for deciding whether developer tools and agent resources are suitable for a curated collection. It checks real repositories, installation paths, activity, duplicates, and security boundaries using evidence.
api-tester
A tool for creating and checking API tests from the real API contract and implementation. An API is the agreed way that software sends requests and receives responses.
env-manager
An environment-variable manager for project settings stored outside the code, often in .env files. It checks variable definitions and usage while keeping secret values out of reports and terminal output.
eslint-fix
A project-aware assistant for finding and fixing ESLint errors, warnings, and configuration compatibility problems. ESLint is a tool that checks JavaScript and TypeScript code for style and common mistakes.
git-workflow
A guide for handling Git repository work safely, including status checks, branches, commits, pushes, pull requests, and rebasing. Git is a version-control system that records code changes and coordinates work between developers.