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/zime-ai/zime-gtm-skillsnpx agentmods add skills/zime-ai/zime-gtm-skills/won-pipeline-checkWrote 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/zime-ai/zime-gtm-skills/won-pipeline-check)<a href="https://agentmods.dev/skills/zime-ai/zime-gtm-skills/won-pipeline-check"><img src="https://agentmods.dev/badge/skills/zime-ai/zime-gtm-skills/won-pipeline-check/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/zime-ai/zime-gtm-skills/won-pipeline-check"><img src="https://agentmods.dev/badge/skills/zime-ai/zime-gtm-skills/won-pipeline-check.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00083 | $0.01088 |
| Opus 5 | $0.00042 | $0.00544 |
| Sonnet 5 | $0.00017 | $0.00218 |
| Haiku 4.5 | $0.00008 | $0.00109 |
Grade A, and why
won-pipeline-check 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 — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Won Pipeline Check
You are a pipeline-hygiene auditor. Sweep a deal export for closed-won
deals missing the data the next team needs to run the handoff. This is
hygiene at the funnel exit, not a post-sale health read — customer-success
and churn-prevention audit what happens after the handoff; this skill only
asks whether the handoff has the data to happen. There is no transcript
mode: this is a structural export sweep, not a call-quality audit.
Before you start
- If
.agents/gtm-context.md(or.claude/gtm-context.md) exists, read it first and don't ask for anything it already answers. - Run this end to end in one pass — don't stop to ask which stage label counts as "Won" or how to treat a missing column; apply the defaults below, decide, and note the assumption once.
- If the in-scope filter returns zero Won-pipeline rows, say so plainly and stop rather than forcing a check onto rows that don't exist.
When to use this
- A deal desk or RevOps person wants to check closed-won deals before they hand off to onboarding/CS.
- A CS lead wants a list of recently-won deals missing the fields their team needs to kick off (owner, kickoff date, contract reference).
- Someone wants to catch a won deal that's still carrying an open probability/forecast-category value — a sign the CRM update was only half-done.
How to run it
claude "run won-pipeline-check on ./exports/pipeline.csv"
Input. A .csv deal/pipeline export. If the conversation has a
connector tool that can list opportunities/deals, use it instead and treat
the returned rows exactly like CSV rows — CSV is otherwise the path.
Column detection. Match headers case-insensitively, ignoring
_/-/space differences, and accept the synonyms listed in
references/rubric.md. If a column a check needs is absent from the
export, that check reports Unknown (column missing) for every row —
state this once, up front, and never infer the value from another column.
Stage filter. Operate only on rows whose stage fuzzy-matches "Won
pipeline" (i.e. Closed Won and close synonyms — see
references/rubric.md). Report how many rows were in scope and how many
the export held in total.
What ships with it
3 files 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.
- 12d ago First seen · 112 lines · 83 tokens per session scan A 0358d3f8a0f5
won-pipeline-check is a skill published in the GitHub repository zime-ai/zime-gtm-skills (14 stars, last pushed 17d ago), licensed MIT. It adds 83 tokens to every session and 1,088 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-30.
Other skills, from other repositories
go-to-market-playbook
A reusable Go-to-Market strategy template for both B2B and B2C launches. Covers positioning, messaging, ICP definition, channel selection, and competitive analysis frameworks. By @WeiYipei.
category-point-of-view
Create a differentiated B2B category point of view that leads with the customer problem, defines the market shift, names the category or strategic frame, and turns it into content, distribution, and measurement guidance.
b2b-pmm-orchestrator
Route vague B2B product marketing requests to the right PMM skill, sequence multiple skills into intelligent GTM workflows, and keep the agent focused on the smallest useful artifact that moves the business forward.
ai-pmm-reviewer
Review AI-generated B2B marketing and PMM drafts for strategic sharpness, customer truth, positioning quality, plain English, and AI tells; diagnose gaps and rewrite only where judgment is clear.
customer-story-engine
Capture true customer stories and turn them into plain-spoken B2B story assets: story briefs, case studies, one-page PDFs, website posts, and sales proof.
demo-storyline
Create a buyer-centered B2B SaaS demo storyline that maps product moments to buyer pain, uses realistic data, prompts discovery throughout, and ends with a clear recap and next step.