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 anhnguyen0905/codex-mcp --skill sales-pipeline-crmgit clone --depth 1 https://github.com/anhnguyen0905/codex-mcpWrote 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/anhnguyen0905/codex-mcp/sales-pipeline-crm)<a href="https://agentmods.dev/skills/anhnguyen0905/codex-mcp/sales-pipeline-crm"><img src="https://agentmods.dev/badge/skills/anhnguyen0905/codex-mcp/sales-pipeline-crm/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/anhnguyen0905/codex-mcp/sales-pipeline-crm"><img src="https://agentmods.dev/badge/skills/anhnguyen0905/codex-mcp/sales-pipeline-crm.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.00087 | $0.01283 |
| Opus 5 | $0.00044 | $0.00642 |
| Sonnet 5 | $0.00017 | $0.00257 |
| Haiku 4.5 | $0.00009 | $0.00128 |
Grade A, and why
sales-pipeline-crm 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 12d 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 — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sales Pipeline & CRM (stages, qualification, forecasting, hygiene)
Stages are exit criteria, not feelings
A pipeline stage is defined by a verifiable event that has already happened, never by seller optimism. "Negotiation" means a proposal was sent and the buyer responded to it — not "I think they're close."
Example B2B ladder (adapt, but keep every criterion buyer-verified):
Lead → fits ICP, contact responded
Qualified → need + budget authority + timeline confirmed by the buyer (BANT), or
MEDDIC fields populated (Metrics, Economic buyer, Decision criteria/process,
Identified pain, Champion)
Evaluation → buyer actively evaluating: demo done, success criteria agreed in writing
Proposal → priced proposal delivered to the economic buyer
Commit → verbal yes + paper process (legal/procurement) started
Closed won/lost
If a deal can sit in a stage with nothing the buyer did to earn it, the stage measures seller mood and every downstream number is fiction.
Pipeline math — definitions
stage conversion = deals exiting stage forward / deals entering stage (cohort-based, by entry
month — a snapshot ratio mixes deal generations)
sales cycle = days from qualified → closed (report median; the mean is hostage to zombies)
weighted pipeline = Σ (deal value × stage probability), probability from YOUR historical
stage→win rates, not the CRM vendor defaults
pipeline coverage = open qualified pipeline / quota for the period (healthy ≈ 3–4×, but derive
from your own win rate: coverage needed = 1 / win rate from qualified)
win rate = won / (won + lost), qualified deals only — counting raw leads flatters nobody
consistently
velocity = (# qualified deals × avg deal size × win rate) / sales cycle days
Forecast three ways and reconcile: weighted pipeline, rep commit roll-up, and trend (last N periods' actuals vs pipeline at the same point in cycle). When they disagree, the trend number usually wins.
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.
- 12d ago First seen · 106 lines · 87 tokens per session scan A 7050e87a5e2c
sales-pipeline-crm is a skill published in the GitHub repository anhnguyen0905/codex-mcp (3 stars, last pushed 2d ago), licensed MIT. It adds 87 tokens to every session and 1,283 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-08-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…