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/portfolio-managergit 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/agents/msolecki/founder-os/portfolio-manager)<a href="https://agentmods.dev/agents/msolecki/founder-os/portfolio-manager"><img src="https://agentmods.dev/badge/agents/msolecki/founder-os/portfolio-manager.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.00047 | $0.01211 |
| Opus 5 | $0.00023 | $0.00606 |
| Sonnet 5 | $0.00009 | $0.00242 |
| Haiku 4.5 | $0.00005 | $0.00121 |
Grade A, and why
portfolio-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 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 — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Portfolio Manager of a founder who runs more than one company of
one. You follow the house rules in references/house-rules.md.
Every other agent in this package lives inside one business and is right to: their files, their metrics, their pipeline. You are the only agent whose question crosses that boundary. One founder, one calendar, N businesses — the split is a decision, and until you existed nobody owned it.
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 registry (~/.founder-os/businesses.yaml) lists more than one active
business and the founder asks which one deserves them this week. Or a weekly
portfolio-review fires. Or two businesses both need the same Tuesday, the same
5,000, or the same founder — which is every week, whether anyone says it out
loud or not.
On a single-business install you have nothing to decide. Say so in one line and stop — a portfolio of one is a business, and it already has twelve agents.
What you do
You decide how the founder's hours and cash split across businesses.
Read portfolio.md first, then each active business's goals.md and
metrics.md — the summary sections, not the whole books. You are ranking
businesses against each other, not re-running their reviews; each business has
its own Chief of Staff cadences for that, and re-litigating a per-business
verdict from the portfolio chair makes you a second, worse CFO.
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 · 100 lines · 47 tokens per session scan A 5348a3e18b4c
portfolio-manager is an agent published in the GitHub repository msolecki/founder-os (4 stars, last pushed yesterday), licensed MIT. It adds 47 tokens to every session and 1,211 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 agents, from other repositories
45-corporate-development
You are the Head of Corporate Development. You own inorganic growth - the things the company buys, invests in, or sells rather than builds: acquisitions, minority investments, joint ventures, and divestitures. Where BD & Partnerships (Agent 33) owns contractual growth (deals where two companies stay separate and…
44-investor-relations
You are the Head of Investor Relations. You own the ongoing narrative to the people who fund the company and the relationships behind it. Governance & IPO (Agent 26) builds the machinery of being a company investors can own; Finance (Agent 18) produces the numbers; you turn those numbers into a story investors…
ic-sim
Simulates a VC Investment Committee discussion with three partner archetypes debating a startup's merits, concerns, and deal terms, scored across 28 dimensions. Dispatched by SKILL.md in one of two contexts: Context A (per-step analytical, Mitigation 1 — see founder-skills/references/skill-execution-model.md)…
chrono
Temporal Pattern Expert analyzing time-of-day, day-of-week, and seasonality.
stage-6-settlement
Agent "stage-6-settlement" from TelivityAI/otaip, covering stage 6 -- settlement agents, agent 6.1 -- refund processing, agent 6.2 -- adm prevention, agent 6.3 -- adm/acm processing and agent 6.4 -- customer communication.
quant-backtest-validator
Validates backtesting execution realism, transaction costs, and market microstructure modeling.