Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/WARROOM-CEO/COREnpx agentmods add skills/warroom-ceo/core/pipeline-reviewWrote 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/warroom-ceo/core/pipeline-review)<a href="https://agentmods.dev/skills/warroom-ceo/core/pipeline-review"><img src="https://agentmods.dev/badge/skills/warroom-ceo/core/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/warroom-ceo/core/pipeline-review"><img src="https://agentmods.dev/badge/skills/warroom-ceo/core/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.00080 | $0.02012 |
| Opus 5 | $0.00040 | $0.01006 |
| Sonnet 5 | $0.00016 | $0.00402 |
| Haiku 4.5 | $0.00008 | $0.00201 |
Grade A, and why
pipeline-review-th 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 6d 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 — 248 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Language: All user-facing output — responses, summaries, and any text the user will read — must be written in Thai (ภาษาไทย). Internal logic, file paths, code snippets, and technical values remain in English.
/pipeline-review-th
If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.md.
Analyze your pipeline health, prioritize deals, and get actionable recommendations for where to focus.
Usage
/pipeline-review [segment or rep]
Review pipeline for: $ARGUMENTS
If a file is referenced: @$1
How It Works
┌─────────────────────────────────────────────────────────────────┐
│ PIPELINE REVIEW │
├─────────────────────────────────────────────────────────────────┤
│ STANDALONE (always works) │
│ ✓ Upload CSV export from your CRM │
│ ✓ Or paste/describe your deals │
│ ✓ Health check: flag stale, stuck, and at-risk deals │
│ ✓ Prioritization: rank deals by impact and closability │
│ ✓ Hygiene audit: missing data, bad close dates, single-thread │
│ ✓ Weekly action plan: what to focus on │
├─────────────────────────────────────────────────────────────────┤
│ SUPERCHARGED (when you connect your tools) │
│ + CRM: Pull pipeline automatically, update records │
│ + Activity data for engagement scoring │
│ + Historical patterns for risk prediction │
│ + Calendar: See upcoming meetings per deal │
└─────────────────────────────────────────────────────────────────┘
What I Need From You
Option A: Upload a CSV Export your pipeline from your CRM (e.g. Salesforce, HubSpot). Helpful fields:
- Deal/Opportunity name
- Account name
- Amount
- Stage
- Close date
- Created date
- Last activity date
- Owner (if reviewing a team)
- Primary contact
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.
- 6d ago First seen · 248 lines · 80 tokens per session scan A 71fd8cf06c37
pipeline-review-th is a skill published in the GitHub repository WARROOM-CEO/CORE (30 stars, last pushed 5mo ago), licensed MIT. It adds 80 tokens to every session and 2,012 once invoked, about $0.0004 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-09-03.
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.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.