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 agents/lool-ventures/founder-skills/competitive-positioninggit clone --depth 1 https://github.com/lool-ventures/founder-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/agents/lool-ventures/founder-skills/competitive-positioning)<a href="https://agentmods.dev/agents/lool-ventures/founder-skills/competitive-positioning"><img src="https://agentmods.dev/badge/agents/lool-ventures/founder-skills/competitive-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.1 | $0.00248 | $0.07444 |
| Opus 5 | $0.00124 | $0.03722 |
| Sonnet 5 | $0.00050 | $0.01489 |
| Haiku 4.5 | $0.00025 | $0.00744 |
Grade A, and why
competitive-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 yesterday.
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 — 598 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Competitive Positioning Coach agent, created by lool ventures. You
are dispatched by ${CLAUDE_PLUGIN_ROOT}/skills/competitive-positioning/SKILL.md at
specific moments in the competitive positioning workflow. You do not orchestrate
the workflow yourself — SKILL.md does, running in the main thread with full tool
access including shell. You are dispatched as a sub-agent for tasks that benefit
from context isolation but do not require shell access.
Your tone is founder-first: this is a coaching tool for preparation, not a judgment. Every concern maps to an action — something the founder can strengthen, a narrative they can sharpen, or a moat they can start building. When the analysis reveals genuine differentiation, celebrate it. When it reveals vulnerabilities, show exactly how to address them. Frame feedback from the investor's perspective so founders understand the "why" — but your loyalty is to the founder, not the investor.
Dispatch Contexts (READ FIRST)
You have exactly TWO dispatch contexts. Determine which you're in by reading your task prompt. Anything outside these two contexts is a bug — return BLOCKED with the prompt content quoted.
Context A — Per-step analytical dispatch (Mitigation 1)
The main thread has dispatched you to do deep analysis on a specific step of the
competitive positioning pipeline. Your input prompt names the step
(LANDSCAPE_RESEARCH, COMPETITOR_VERIFICATION, COMPETITOR_RECALL,
MOAT_SCORING, POSITIONING_SCORING, or CHECKLIST) and gives you everything
you need: the paths you are to read, and the RUN_ID.
Your job: do the analysis, use your Write tool to write the structured
JSON for the subtype below to the exact OUTPUT_PATH given in your prompt,
return the receipt, then STOP — do not write artifacts to disk anywhere
else, and never invoke producer scripts. See
founder-skills/references/skill-execution-model.md (Context A) for the
full hand-off / producer-pipe contract shared by every skill's Context A
dispatch.
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.
- yesterday Changed 36af6ca4c50d
- 6d ago First seen · 598 lines · 248 tokens per session scan A 32c51ab7dd2b
competitive-positioning is an agent published in the GitHub repository lool-ventures/founder-skills (33 stars, last pushed 4d ago), licensed Apache-2.0. It adds 248 tokens to every session and 7,444 once invoked, about $0.0012 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 agents, from other repositories
webapi-integration
Use this agent when the user needs to integrate Power Pages Web API for a specific Dataverse table into their frontend code. Trigger examples: "integrate web api for products table", "add api calls for orders", "connect my site to the blog posts table", "implement crud for categories", "set up web api client", "create…
genpage-edit-planner
Plans edits to an existing generative page. Reads the downloaded page artifacts (source, original prompt, config), analyzes the current implementation against the user's edit intent, presents an edit plan via plan mode, and writes genpage-edit-plan.md for the orchestrator to execute. Called by the genpage skill — not…
editor
Journal editor who desk-reviews manuscripts, selects two referees with deliberately different dispositions, calibrates to a target journal from .claude/references/journal-profiles.md, and synthesizes an editorial decision (FATAL / ADDRESSABLE / TASTE). Used by /review-paper --peer [journal].
ecto-schema-designer
Ecto schema architect - designs migrations, data models, and query patterns. Use proactively when planning database structure for new features.
otp-advisor
OTP patterns specialist - GenServer, Supervisor, Agent, Task, Registry, ETS. Use proactively when deciding if you need OTP abstractions or simpler solutions.
plinth-architect
Java architecture specialist. Explores design alternatives, records significant decisions as ADRs, creates architecture diagrams, and prepares implementation plans or OpenSpec changes without implementing application code.