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 skills/msolecki/founder-os/relationship-mapnpx skills add msolecki/founder-os --skill relationship-mapgit clone --depth 1 https://github.com/msolecki/founder-osWrote 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/msolecki/founder-os/relationship-map)<a href="https://agentmods.dev/skills/msolecki/founder-os/relationship-map"><img src="https://agentmods.dev/badge/skills/msolecki/founder-os/relationship-map.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 | $0.00035 | $0.02020 |
| Opus 5 | $0.00017 | $0.01010 |
| Sonnet 5 | $0.00007 | $0.00404 |
| Haiku 4.5 | $0.00003 | $0.00202 |
Grade A, and why
relationship-map 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 4d 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 — 164 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Relationship Map
A founder's mental model of their network is the twelve people they saw most recently. The next client is almost always someone else — a past client, delighted eighteen months ago, who has since forgotten what the founder does.
Forgetting is the default, not a judgement. This map exists because the number that predicts the next contract is not warmth. It is days since last real contact, and it is a number nobody keeps.
When to use
Quarterly. Before a conference. When the founder needs an introduction, a reference, or a second opinion and "doesn't know who to ask" — which almost always means they know, and have not thought about that person since 2023. Also whenever cold outreach is proposed while the warm list sits untouched, which is the most expensive form of procrastination available to a solo founder.
Inputs
Read first, in order — house rule 1:
network.md— the current map, and how stale it isclients/— every past client. This is the highest-converting group in any company of one and the most neglected, in that order, causally.pipeline.md— who is a live deal. They are the Pipeline Coach's; they do not belong in the map's cadence.offer.md— the ICP, for who among the network could plausibly referingestion-gate— "what they need" is a claim about another person's situation, which is the gate's hardest case. Heard from them, it is FACT. Heard about them from a third party, it is hearsay and does not enter. Run the gate on every cell before the row exists.
Beliefs
- Relationships decay from asymmetry, not from neglect. Someone contacted only when they are needed is not being neglected, they are being used, and the interval on the calendar looks identical either way.
- Referrals do not come from the people who like the founder most. They come from whoever most recently had a reason to describe them out loud to somebody else. That is a fact about frequency, not about affection, and it is why the delighted client at 640 days refers nobody.
- The founder's network is smaller than they believe and warmer than they fear. Both errors have one cause: they are counting people who never think about them, and avoiding the ones who do.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 4d ago First seen · 164 lines · 35 tokens per session scan A c9495d2305b3
relationship-map is a skill published in the GitHub repository msolecki/founder-os (4 stars, last pushed today), licensed MIT. It adds 35 tokens to every session and 2,020 once invoked, about $0.0002 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…