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/champion-trackerWrote 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/champion-tracker)<a href="https://agentmods.dev/skills/zime-ai/zime-gtm-skills/champion-tracker"><img src="https://agentmods.dev/badge/skills/zime-ai/zime-gtm-skills/champion-tracker/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/champion-tracker"><img src="https://agentmods.dev/badge/skills/zime-ai/zime-gtm-skills/champion-tracker.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.00112 | $0.01406 |
| Opus 5 | $0.00056 | $0.00703 |
| Sonnet 5 | $0.00022 | $0.00281 |
| Haiku 4.5 | $0.00011 | $0.00141 |
Grade A, and why
champion-tracker 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 — 140 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Champion Tracker
You are a deal-intelligence writer. Track champion strength across a
deal's call history. This is a phase-2 deal-intelligence skill — it
applies meddicc's Champion bar longitudinally and per-person instead of
scoring it as one letter in a 7-8 letter scorecard. Where meddicc asks
"is there a champion, this call?", this skill asks "which named contact,
across every call so far, is actually acting like one — and is that
getting stronger or weaker?"
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 without stopping to ask which contacts to track — every named contact who speaks gets evaluated against the Action/ Sentiment test.
- If only one transcript is given, report "insufficient history" for the trend line rather than guessing a direction from a single data point.
When to use this
- A rep wants to know whether a contact who sounds enthusiastic is actually doing anything for the deal, before calling them a champion in a forecast update.
- A manager reviewing a stalled or at-risk deal wants to see whether champion strength is trending up, flat, or eroding across the calls so far.
- Someone prepping a QBR or deal review wants a cited ledger of who did what, instead of a vague "strong stakeholder engagement" line.
Inputs
One or more call transcripts from the same deal. If more than one is given, read them in chronological order — the trend read in the last section depends on call order, not filename order.
Transcript mode (.txt, .vtt, .json, .md)
claude "run champion-tracker on ./calls/call1.txt ./calls/call2.txt"
Read every transcript given, in order. For each named contact who speaks
(not the rep), pull every instance across all calls that is either an
act of internal selling or a statement of positive sentiment — see
references/rubric.md for the exact test and worked examples. A contact
who never says anything that clears either bar gets no row; don't invent
one to pad the ledger.
What ships with it
5 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 · 140 lines · 112 tokens per session scan A 4fff6153a4c9
champion-tracker is a skill published in the GitHub repository zime-ai/zime-gtm-skills (14 stars, last pushed 17d ago), licensed MIT. It adds 112 tokens to every session and 1,406 once invoked, about $0.0006 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.