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 matteotitta/genesys-skills --skill sales-tracksgit clone --depth 1 https://github.com/matteotitta/genesys-skillsWrote 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/matteotitta/genesys-skills/sales-tracks)<a href="https://agentmods.dev/skills/matteotitta/genesys-skills/sales-tracks"><img src="https://agentmods.dev/badge/skills/matteotitta/genesys-skills/sales-tracks/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/matteotitta/genesys-skills/sales-tracks"><img src="https://agentmods.dev/badge/skills/matteotitta/genesys-skills/sales-tracks.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.00181 | $0.03473 |
| Opus 5 | $0.00090 | $0.01736 |
| Sonnet 5 | $0.00036 | $0.00695 |
| Haiku 4.5 | $0.00018 | $0.00347 |
Grade A, and why
sales-tracks 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 9d 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 — 261 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sales tracks
Persona-specific sales pitch tracks for live discovery and demo conversations. Each track is a single page the rep scans 60 seconds before a call: who they're talking to, the story arc to open with, the capability sequence to land, the objections they'll hear (with verbatim transcript quotes), the competitor moves to counter, and the discovery questions that confirm fit.
The body of this file holds decision-grade context (when to invoke, inputs, output structure, anti-Frankenstein guardrails, gotchas). Step-by-step process, output template, quality gates, and iteration prompts live in the premium reference.
This is the persona-axis sales artifact, complementing battlecards (competitor-axis), sales-deck (full pitch deck), and demo-script (product demo flow). A rep typically uses two together: sales-tracks for "who am I selling to," battlecards for "they brought up [competitor]."
Doctrine inherited (Step 7 — 0626 rollout)
Output complies with:
output-tenets.md— the seven tenetsoutput-simplicity.md— length caps, three-layer source placement, robot-tells bandoc-output-structure.md— GDoc/Notion structural defaults (when published)- Step 6 calibration: see [[feedback_execution_doctrine_refinements_step6]]
Refinements applied to this skill:
| Code | Refinement | How it lands in sales-tracks |
|---|---|---|
| R1 | Source placement (three layers) | Rep-facing working markdown stays internal-inline cited (auditability). Published Notion playbook is a client-team surface — sources move to a collapsed "Sources" toggle at the bottom of each persona track. No [VERIFIED:...] tags inline in the face doc. |
| R3 | Product-update tone | §3 capability pitches default to "we shipped X to address Y" framing. Never "we're thrilled to announce." Even Tier 1 features get product-update tone. |
| R6 | CTA hierarchy | §7 discovery questions end with the stage-appropriate next step — trial/sign-up for cold prospects, product-action for warm-base accounts already in motion. Never blog or PDF as primary CTA. |
| R9 | Action-oriented section names | Section names already verb-led (Story arc, Capability pitch, Objection handlers, Discovery questions). Preserve — do not rename to status-oriented variants ("Overview," "Background"). |
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.
- 9d ago First seen · 261 lines · 181 tokens per session scan A 814d07551ea0
sales-tracks is a skill published in the GitHub repository matteotitta/genesys-skills (36 stars, last pushed 1mo ago), licensed MIT. It adds 181 tokens to every session and 3,473 once invoked, about $0.0009 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
gingiris-b2b-growth
🇺🇸 B2B SaaS Growth — PLG vs SLG Playbook — Diagnose whether your problem is distribution, pricing, or PMF. PLG/SLG selection by ACV and sales cycle, the 5-stage path from $0 to $10M ARR, NRR discipline, affiliate & channel motion, enterprise tiering. Built from HeyGen, Deel, Vercel, Supabase, Snowflake patterns.…
gr-b2b-growth
A guide to growing a business-to-business software product from early user research to large-scale sales. B2B software is sold to companies rather than individual consumers.
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.
gingiris-go-global
🇺🇸 AI Product / SaaS Go-Global Complete SOP — From competitor research to launch to monetization. A full-cycle playbook covering Phase 0-5 (market validation, positioning, first 100 users, user interviews, beta-to-growth) plus open-source launch, Product Hunt, Reddit, SEO/GEO, conversion, and org principles.…
gr-competitor-research
Your competitor just launched. You have no idea how they grew so fast. Should you reverse-engineer their website? Track their social media? Map their growth flywheel? This gives you the complete SOP — from Wayback Machine snapshots to X/Twitter propagation analysis to growth flywheel scoring. Built from 150+ AI…
ai-launch-playbook
Launch your AI product to global attention — the playbook behind Manus, Devin, and AFFiNE's breakout launches. Covers AI-specific GTM strategy, hype cycle management, waitlist tactics, and multi-market rollout for maximum day-one impact.