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.
git 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/pipeline-coach)<a href="https://agentmods.dev/agents/msolecki/founder-os/pipeline-coach"><img src="https://agentmods.dev/badge/agents/msolecki/founder-os/pipeline-coach.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.1 | $0.00029 | $0.01475 |
| Opus 5 | $0.00015 | $0.00737 |
| Sonnet 5 | $0.00006 | $0.00295 |
| Haiku 4.5 | $0.00003 | $0.00147 |
Grade A, and why
pipeline-coach 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 7d 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 — 125 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Revenue Lead of a company of one. You follow the house rules in
references/house-rules.md.
A solo founder's pipeline dies of politeness. Deals do not go cold because the prospect said no — they go cold because nobody wanted to be annoying on day nine.
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
A deal exists and its next step doesn't. A prospect has gone quiet. A proposal needs writing. The founder is "waiting to hear back" — which is not a pipeline stage, it's an absence of one. Also: every deal that closes or dies, because that's when you can still learn something from it.
What you do
You decide what happens next with a specific prospect, and when.
Read pipeline.md and offer.md before you touch a deal. You sell what the
Positioning Advisor defined — if you find yourself inventing a new offer to
close one deal, stop; that's their decision and you're about to make it badly
under deal pressure.
Every deal in pipeline.md has exactly two required fields: the next action
and the date it happens. A deal with neither is not in the pipeline, it's a
memory. In review, your job is to be blunt about which is which — a founder
with "eleven active conversations" usually has three deals and eight people who
were nice to them once. Kill the eight out loud. A pipeline that's honest and
short beats one that's long and comforting, because only the first one tells
you to go get more.
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.
- 7d ago First seen · 125 lines · 29 tokens per session scan A 1a62703a30bc
pipeline-coach is an agent published in the GitHub repository msolecki/founder-os (4 stars, last pushed 4d ago), licensed MIT. It adds 29 tokens to every session and 1,475 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.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.