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 skills add msolecki/founder-os --skill pipeline-reviewgit 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/pipeline-review)<a href="https://agentmods.dev/skills/msolecki/founder-os/pipeline-review"><img src="https://agentmods.dev/badge/skills/msolecki/founder-os/pipeline-review/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/msolecki/founder-os/pipeline-review"><img src="https://agentmods.dev/badge/skills/msolecki/founder-os/pipeline-review.svg" alt="Reviewed on agentmods" width="80" 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.00036 | $0.02859 |
| Opus 5 | $0.00018 | $0.01430 |
| Sonnet 5 | $0.00007 | $0.00572 |
| Haiku 4.5 | $0.00004 | $0.00286 |
Grade A, and why
pipeline-review 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 10d 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 — 214 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pipeline Review
A founder with "eleven active conversations" has three deals and eight people who were nice to them once. The eight are not harmless: they are what lets the founder feel busy at exactly the moment they should be alarmed.
Every deal has two required fields — the next action, and the date it happens. A deal with neither is not in the pipeline, it is a memory. This review's output is the killing.
When to use
Weekly. Fired by the local scheduler after setup-cadences; otherwise run
pipeline-review by hand. Also before any
quarterly planning that assumes revenue, and whenever the founder is "waiting to
hear back" — which is not a pipeline stage, it is the absence of one.
Inputs
Read first, in order — house rule 1:
pipeline.md— every entry, including the ones that have been there since springoffer.md— what is actually being sold, and the ICP. Deals outside the ICP get named as such.goals.md— this quarter's revenue bet. The gap is what the pipeline is measured against.metrics.md— cash and burn, for what the gap actually meansingestion-gate— every line in## Liveis something a prospect said, and a prospect is the counterparty. Run the gate on each before it goes in the file: it decides the tier and the stamp, this skill decides whether the deal survives. "They're keen" is its named failure mode and this is the file it names.
Beliefs
- Deals do not die of neglect. They die at a specific moment, in a specific conversation, and the founder was present for it. "Went quiet" describes the founder's attention, not the prospect's decision.
- A pipeline does not exist to forecast revenue. It exists to say how many weeks remain to fix the quarter. Reviewed for accuracy it is a report; reviewed for lead time it is a decision, and only one of those was worth the hour.
- An honest empty pipeline is better news than a full one made of maybes. The founder can act on nothing. They cannot act on eight things that are secretly nothing, because every one of them comes with a plausible reason to wait.
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.
- 10d ago First seen · 214 lines · 36 tokens per session scan A c03c7c5d1399
pipeline-review is a skill published in the GitHub repository msolecki/founder-os (4 stars, last pushed 7d ago), licensed MIT. It adds 36 tokens to every session and 2,859 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
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
remove
Remove a deployed framework or addon from the current workspace.