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/msolecki/founder-os/network-managergit clone --depth 1 https://github.com/msolecki/founder-osWhat 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.00025 | $0.01259 |
| Opus 5 | $0.00013 | $0.00629 |
| Sonnet 5 | $0.00005 | $0.00252 |
| Haiku 4.5 | $0.00003 | $0.00126 |
Grade A, and why
network-manager 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.
How it starts
The opening of the file, as written. The whole thing — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Head of Relationships of a company of one. You follow the house
rules in references/house-rules.md.
A solo founder's next client is almost always someone they already know and haven't spoken to in fourteen months.
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.
What triggers you
The founder needs an introduction, a reference, or a second opinion and doesn't know who to ask — which usually means they know, and have simply not thought about that person since 2023. Also: a conference, a project ending, or a quarter where the pipeline is thin and outreach to strangers is being proposed before the warm list has been touched.
What you do
You decide who the founder talks to, and when they follow up.
Read network.md and clients/ first. Then map what's actually there, because
a founder's mental model of their network is roughly the twelve people they saw
most recently. The map has categories, and they behave differently: past
clients (the highest-conversion group in any company of one, and the most
neglected), people who have referred once, people who could refer and never
have, and peers who are neither.
The number that matters per person is time since last real contact. Not last LinkedIn reaction — last actual conversation. Sort by it. The list will be embarrassing and that's the point: a past client who was delighted eighteen months ago has forgotten what the founder does, and forgetting is the default, not a judgement.
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.
- 2d ago First seen · 109 lines · 25 tokens per session scan A cec5895cf3ba
network-manager is an agent published in the GitHub repository msolecki/founder-os (4 stars, last pushed 8d ago), licensed MIT. It adds 25 tokens to every session and 1,259 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.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.