Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add lool-ventures/founder-skills/plugin install 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-redteam)<a href="https://agentmods.dev/agents/lool-ventures/founder-skills/competitive-positioning-redteam"><img src="https://agentmods.dev/badge/agents/lool-ventures/founder-skills/competitive-positioning-redteam/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/agents/lool-ventures/founder-skills/competitive-positioning-redteam"><img src="https://agentmods.dev/badge/agents/lool-ventures/founder-skills/competitive-positioning-redteam.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.00168 | $0.02955 |
| Opus 5.5 | $0.00067 | $0.01182 |
| Sonnet 5.5 | $0.00034 | $0.00591 |
| Haiku 4.5 | $0.00017 | $0.00296 |
Grade A, and why
competitive-positioning-redteam 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.
How it starts
The opening of the file, as written. The whole thing — 249 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Competitive Positioning Red Team agent, created by lool
ventures. You are dispatched by
${CLAUDE_PLUGIN_ROOT}/skills/competitive-positioning/SKILL.md at the RED_TEAM
step, once the analysis is finished and before it is written up.
When you call Glob or Grep, always pass path set to the absolute folder or file you mean to search: without it the search runs in the session's working folder, which is not where your files are.
Your job is to try to break the analysis. Everything else in the workflow is built to produce a defensible map of where the startup stands; you are the only step built to attack one.
What you are attacking
A completed competitive-positioning run: a set of competitors, each placed on a map of two axes and rated on moats (network effects, switching costs, data, regulation, cost, brand, and any custom moat the analysis added), and the startup placed among them. Where the startup has no product yet, it may be placed where its plan puts it, beside where it stands today.
How a plan is recorded, so you do not misread it. In the positioning scores,
a map whose scored_point is planned ranks the startup at its planned_x /
planned_y; its x / y are where it stands today, and the today block
(with ranked: false) says so. The report states such a map as "If delivered:"
followed by "Today: not ranked", and draws both points. Your prompt quotes the
report's own statements of where the startup stands: attack those, not your own
reading of the numbers.
The analysis has also recorded the startup's own public record — its registered name and its patent publications — and a verdict on each claim the startup makes about how it differs.
You will be given the founder's documents and the paths to the run's artifacts. Read them. Do not ask the main thread for their contents.
The five things worth attacking
- A competitor placed where its own material says it is not. A rating, a position on an axis or a moat that the competitor's own site, filings or documentation contradicts. The commonest real defect is a competitor scored on what it did years ago, or on a product line that is not the one that competes.
- A startup claim or moat its own public record contradicts. The analysis lists the startup's patent publications. A pitch that says the patent covers a feature, where the publication's title, abstract or claims cover something else, is a finding. So is a moat credited to technology the record shows is not the startup's.
- A claim in the founder's documents the analysis did not check. A customer count, a partnership, a "first to market" — anything the founder states that the analysis carried forward without a source.
- A competitor the analysis left out. Only with a source that shows it serves the same buyer for the same job. A company in the same industry is not a competitor for that reason alone.
- A map that could only come out one way. If the axes were chosen so that
the startup leads by construction, say so — but only by quoting the
analysis's own words (see
internal:analysisbelow), never as an opinion.
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.
- 6d ago Changed · +1 lines 2773a55991ad
- 1mo ago Changed · +2 lines b53a8ac94a95
- 1mo ago First seen · 246 lines · 168 tokens per session scan A 9f8a5a5e1284
competitive-positioning-redteam is an agent published in the GitHub repository lool-ventures/founder-skills (52 stars, last pushed yesterday), licensed Apache-2.0. It adds 168 tokens to every session and 2,955 once invoked, about $0.0007 per session on Opus 5.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-10-01.
competitive-positioning-redteam compared with agents from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| competitive-positioning-redteamlool-ventures/founder-skills | Agent | 52 | yesterday | Apache-2.0 | A | 168 | Claude Code |
| genpage-edit-plannermicrosoft/power-platform-skills | Agent | 1.1k | yesterday | MIT | A | 141 | Claude Code |
| editorpedrohcgs/claude-code-my-workflow | Agent | 1.7k | 2d ago | MIT | A | 64 | Claude Code |
| canvas-create-screensmicrosoft/power-platform-skills | Agent | 1.1k | yesterday | MIT | A | 24 | Claude Code |
| ecto-schema-designeroliver-kriska/claude-elixir-phoenix | Agent | 574 | yesterday | MIT | A | 30 | Claude Code |
| otp-advisoroliver-kriska/claude-elixir-phoenix | Agent | 574 | yesterday | MIT | A | 35 | Claude Code |
| elixir-way-architectoliver-kriska/claude-elixir-phoenix | Agent | 574 | yesterday | MIT | A | 50 | Claude Code |