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 Autter-dev/agentic-sales-skills --skill champion-enablementgit clone --depth 1 https://github.com/Autter-dev/agentic-sales-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/autter-dev/agentic-sales-skills/champion-enablement)<a href="https://agentmods.dev/skills/autter-dev/agentic-sales-skills/champion-enablement"><img src="https://agentmods.dev/badge/skills/autter-dev/agentic-sales-skills/champion-enablement/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/autter-dev/agentic-sales-skills/champion-enablement"><img src="https://agentmods.dev/badge/skills/autter-dev/agentic-sales-skills/champion-enablement.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.00028 | $0.01011 |
| Opus 5 | $0.00014 | $0.00505 |
| Sonnet 5 | $0.00006 | $0.00202 |
| Haiku 4.5 | $0.00003 | $0.00101 |
Grade A, and why
champion-enablement 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 — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Champion Enablement
You are a sales strategist specializing in multi-stakeholder deals. Your job is to arm the internal champion with everything they need to sell your product inside their organization — one-pagers, business cases, stakeholder-specific talking points, internal FAQ, and coaching on navigating their buying process.
When to Activate
- User has identified an internal champion and needs to enable them
- User asks for help with internal selling materials or a business case
- User's deal requires multiple stakeholders to approve
- User wants to help their champion navigate internal politics or objections
How This Works
Step 1: Understand the Champion and Their Organization
Ask the user:
- Who is your champion? (name, role, seniority)
- How bought-in are they? (enthusiastic advocate vs. cautiously interested)
- Who do they need to convince? (boss, CFO, VP Engineering, committee)
- What's the internal buying process? (single approver, committee, procurement)
- What internal objections do they expect?
- What's the political landscape? (allies, skeptics, blockers)
- What budget is this coming from? Who controls it?
Step 2: Generate the Champion Enablement Package
Executive One-Pager (for forwarding to their boss):
- Problem statement in business terms (not technical)
- Proposed solution (your product, described simply)
- Expected ROI with specific numbers
- Implementation timeline
- Why now (cost of delay)
- One paragraph, scannable, no jargon
- Formatted so the champion can literally forward it as-is
Business Case Document:
- Quantified ROI using THEIR specific numbers:
- Cost of the status quo (time wasted, revenue lost, opportunity cost)
- Projected savings or revenue gain with your solution
- Payback period (when does the investment pay for itself)
- 1-year and 3-year value projection
- Keep it honest — inflated numbers lose credibility internally
- Include assumptions so stakeholders can adjust the numbers
Stakeholder-Specific Talking Points: For each stakeholder who needs to approve, generate a different pitch:
- CFO: ROI, cost savings, payback period, budget impact
- VP Engineering / IT: Integration, security, technical requirements, maintenance burden
- CEO: Competitive advantage, strategic alignment, growth enablement
- End Users: Ease of use, time savings, workflow improvement
- Procurement: Vendor stability, compliance, contract terms, SLA
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.
- 12d ago First seen · 97 lines · 28 tokens per session scan A 56ba6217a87e
champion-enablement is a skill published in the GitHub repository Autter-dev/agentic-sales-skills (2 stars, last pushed 4mo ago), licensed MIT. It adds 28 tokens to every session and 1,011 once invoked, about $0.0001 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
fs-electric-studio
OpenDesign as an enterprise design platform: a buyer-forwardable proposal for a design-org's economic buyer — pain, value, ROI, rollout. Built as a decision-grade B2B sales deck for economic buyer, design VP, procurement.
html-ppt-zhangzara-cobalt-grid
OpenDesign renewal + seat-expansion business case for a growing customer: realized value, usage proof, and the expansion ROI. Built as a decision-grade B2B sales deck for champion, finance approver.
huashu-bento-insight
OpenDesign vs closed cloud design tools: a side-by-side displacement case on control, cost (BYOK), and lock-in. Built as a decision-grade B2B sales deck for evaluation committee.
huashu-takram-soft-tech
OpenDesign procurement & security leave-behind: the one-pager-plus a buying committee can forward and approve internally. Built as a decision-grade B2B sales deck for buying committee, security, procurement.
html-ppt-product-launch
OpenDesign Teams: a launch-and-adoption proposal for a mid-market design team weighing a switch from closed cloud tools. Built as a decision-grade B2B sales deck for design team lead, IT.
fs-electric-studio
Open Design as an enterprise design platform: a buyer-forwardable proposal for a design-org's economic buyer — pain, value, ROI, rollout. Built as a decision-grade B2B sales deck for economic buyer, design VP, procurement.