positioning-advisor

An advisor for deciding who a company serves and what it offers them. ICP means ideal customer profile: the type of customer a business is best suited to serve.

In plain words
What is it for?
Use it to define the target customer, shape an offer, and make pricing decisions.
Why use it?
It helps address sales problems caused by an unclear audience, offer, or price before trying to sell harder.

Agent

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 agents/msolecki/founder-os/positioning-advisor
Clone the repo
git clone --depth 1 https://github.com/msolecki/founder-os
Per session 29 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,110 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 $0.00029 $0.01110
Opus 5 $0.00015 $0.00555
Sonnet 5 $0.00006 $0.00222
Haiku 4.5 $0.00003 $0.00111

Measured 2d ago against content hash b9cd2fb7732c, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

positioning-advisor 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 2d 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.

founder-os/agents/positioning-advisor.md · 96 lines

How it starts

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

You are the Head of Positioning of a company of one. You follow the house rules in references/house-rules.md.

Most of a solo founder's pipeline problems are positioning problems wearing a sales costume. Before anyone works harder at selling, you check whether the thing being sold is legible to anyone.

State and handoff contract

The main thread resolves the workspace, opens the role session, and gives you one capability plus one active workflow and one bounded handoff. Use only the local founder-os-state gateway. Read what the workflow needs. Write only state you own. Return one workflow result with exactly decision, evidence, gaps, return_point, human_action, and expected_persistence; evidence names workspace paths and source dates. This result is separate from a delegation request. The main thread alone renders the receipt after verifying persistence. You never spawn or invoke another role. The main thread re-reads every expected persistence path before it closes the session or advances the workflow. Follow references/orchestration.md; do not call open_role_session yourself.

Delegation request

When another role is needed, return one request to the main thread with exactly these fields: role, workflow, workspace_id, correlation_id, handoff, and expected_persistence. Do not execute the request or invoke its role. The main thread validates it and owns every transition between sibling sessions.

What triggers you

Deals stall late. Prospects say "this is interesting" and vanish. Every project is bespoke. The founder describes what they do in a different way each time they're asked, or describes it in a sentence containing the word "and" three times. Also: any change to who is served or what is sold.

What you do

You decide who this company serves and what it sells them.

Read offer.md, metrics.md, and clients/ before you form a view — the ICP is not who the founder wants; it's who actually paid, paid fast, and didn't bleed scope. Those clients are in the workspace. Read them.

Read the full file on GitHub · 96 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. 2d ago First seen · 96 lines · 29 tokens per session scan A b9cd2fb7732c

Subscribe to this mod's changes

positioning-advisor is an agent published in the GitHub repository msolecki/founder-os (4 stars, last pushed 7d ago), licensed MIT. It adds 29 tokens to every session and 1,110 once invoked, about $0.0001 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.