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 varunk130/ai-gtm-skill-library --skill position-lockgit clone --depth 1 https://github.com/varunk130/ai-gtm-skill-libraryWrote 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/varunk130/ai-gtm-skill-library/position-lock)<a href="https://agentmods.dev/skills/varunk130/ai-gtm-skill-library/position-lock"><img src="https://agentmods.dev/badge/skills/varunk130/ai-gtm-skill-library/position-lock/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/varunk130/ai-gtm-skill-library/position-lock"><img src="https://agentmods.dev/badge/skills/varunk130/ai-gtm-skill-library/position-lock.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.00052 | $0.01218 |
| Opus 5 | $0.00026 | $0.00609 |
| Sonnet 5 | $0.00010 | $0.00244 |
| Haiku 4.5 | $0.00005 | $0.00122 |
Grade A, and why
position-lock 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 9d 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 — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Position Lock (PRISM Framework)
Engineer a positioning architecture that is structurally defensible and cascades consistently from brand level down to feature level.
When to Use
- New product positioning
- Repositioning after market shift
- Messaging overhaul
- Pre-launch messaging lock
- Category creation strategy
What You'll Need
Critical inputs (ask if not provided):
- Product/company to position
- Target audience (primary persona)
- Top 2-3 competitors
Nice-to-have:
- Battle Scanner output (competitive positioning)
- Whitespace Finder output (opportunities to position around)
- Journey Architect output (persona needs at each stage)
Process
Step 1: Build the 4-Layer Positioning Stack
Layer 1: Category Design Decide your category strategy:
| Strategy | When to Use | Risk Level |
|---|---|---|
| Create new category | You are truly different, market is ready | High effort, highest leverage |
| Redefine existing category | Existing category is stale, you have a fresh angle | Medium effort |
| Compete within category | Category is well-understood, you have clear advantages | Lowest effort |
Layer 2: Strategic Narrative The "big idea" connecting your product to a larger market shift:
- NOT a feature story -- a worldview story
- Format: "The world is changing from [old way] to [new way]. [Product] is built for the new world."
- Must feel inevitable and bigger than your product
Layer 3: Value Proposition Matrix
| Value Type | Question It Answers | Example |
|---|---|---|
| Functional | What does it DO? | "Automates X, reducing time by 80%" |
| Emotional | How does it make them FEEL? | "Confidence that nothing falls through cracks" |
| Social | How does it make them LOOK? | "Seen as innovative by leadership" |
| Economic | What does it SAVE/EARN? | "Saves $50K/year per team" |
Layer 4: Proof Architecture Map evidence to every value claim:
- Metrics and data points
- Customer case studies
- Third-party validation (analyst quotes, awards)
- Product demonstrations
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.
- 9d ago First seen · 108 lines · 52 tokens per session scan A ec20713608ec
position-lock is a skill published in the GitHub repository varunk130/ai-gtm-skill-library (5 stars, last pushed 1mo ago), licensed MIT. It adds 52 tokens to every session and 1,218 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-31.
Other skills, from other repositories
session-deep-dive
Deep qualitative analysis of high-signal sessions. Spawns subagents with v2 template, synthesizes patterns, compares against known findings. Use after /session-scan.
brainstorm
Brainstorm Elixir/Phoenix features — explore ideas, compare approaches, gather requirements. Use when vague idea, not sure how to approach, or want to discuss before plan.
plugin-dev-workflow
Guide plugin development workflow — editing skills, agents, hooks, or eval framework in this repo. Use when modifying files in plugins/elixir-phoenix/, lab/eval/, or lab/autoresearch/. Ensures changes pass eval, lint, and tests before committing.
elixir-idioms
OTP/BEAM patterns and Elixir idioms — GenServer, Supervisor, Task, Registry, pattern matching, with chains, pipes. Use when designing processes or debugging BEAM issues.
tidewave-integration
Tidewave MCP runtime tools — debugging, smoke testing, live state inspection, SQL queries, hex docs. Use when evaluating code in a running Phoenix app.
110-java-maven-best-practices
Use when you need to review, improve, or troubleshoot a Maven pom.xml file — including dependency management with BOMs, plugin configuration, version centralization, multi-module project structure, build profiles, or any situation where you want to align your Maven setup with industry best practices. This should…