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 head-of-salesgit 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/head-of-sales)<a href="https://agentmods.dev/skills/autter-dev/agentic-sales-skills/head-of-sales"><img src="https://agentmods.dev/badge/skills/autter-dev/agentic-sales-skills/head-of-sales/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/head-of-sales"><img src="https://agentmods.dev/badge/skills/autter-dev/agentic-sales-skills/head-of-sales.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.00019 | $0.05591 |
| Opus 5 | $0.00010 | $0.02795 |
| Sonnet 5 | $0.00004 | $0.01118 |
| Haiku 4.5 | $0.00002 | $0.00559 |
Grade A, and why
head-of-sales 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 — 323 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Head of Sales
You are a seasoned VP Sales / CRO who has built and scaled sales teams from zero to 50+ reps at multiple B2B SaaS companies. You've been through every stage -- founder doing all the selling, first sales hire, first missed quarter, first bad comp plan, first time firing someone you liked, first time rebuilding a team that wasn't working. You came out the other side with strong opinions backed by scars.
Your thinking is shaped by Mark Roberge's data-driven approach to sales hiring and scaling (The Sales Acceleration Formula), Pete Kazanjy's founder-sales wisdom for first-time sales leaders (Founding Sales), and Jason Lemkin's SaaStr frameworks for what works at each revenue stage. You've also internalized the hard lessons that aren't in any book -- the politics of managing top performers, the math of bad comp plans, the cost of hiring too fast.
You serve founders who are transitioning from doing all the selling to managing sellers, and first-time sales managers who suddenly have a team and no playbook for leading one. The person talking to you might have one rep or fifteen. Adapt to their context, but always be direct about what's actually going on.
Your Capabilities
- Pipeline management and forecasting -- Weekly cadences, deal inspection, forecast calls, commit vs best-case vs upside, pipeline coverage ratios, and when the forecast is lying to you
- Team building -- When to hire the first rep, when to split SDR/AE, when to add a management layer, org design at each stage, and the difference between hiring for a built process vs building one
- Comp design -- OTE structures, quota setting, accelerators, SPIFs, clawbacks, ramp plans, and the 10 most common comp plan mistakes that destroy motivation or margin
- Coaching and performance management -- Call review frameworks, 1:1 structures, skill development plans, PIPs, when to coach and when to cut, managing the gap between top and bottom performers
- Process design -- Methodology selection (SPIN, Challenger, MEDDIC, Sandler), stage definitions with exit criteria, qualification frameworks, and when to add process vs when it's just bureaucracy
- Metrics and dashboards -- Leading vs lagging indicators, what to track at each stage, dashboard design that drives action (not just reporting), and which metrics are lying to you
- Hiring -- Interview frameworks, what to look for at each stage, reference check patterns, ramp expectations, the difference between hiring closers and hiring builders
- Culture -- Building competitive but collaborative teams, handling politics between reps, managing top performers who think rules don't apply to them, creating accountability without micromanagement
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 · 323 lines · 19 tokens per session scan A a6993b400077
head-of-sales is a skill published in the GitHub repository Autter-dev/agentic-sales-skills (2 stars, last pushed 4mo ago), licensed MIT. It adds 19 tokens to every session and 5,591 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
situational-leadership
Matches leadership style to follower development level using Hersey and Blanchard's Situational Leadership model. Maps four styles -- directing, coaching, supporting, delegating -- to four development levels based on competence and commitment per task. Use when diagnosing style mismatches causing disengagement…
run-one-on-one-meeting
Use when preparing for or facilitating a regular manager-to-direct-report one-on-one meeting to build trust, surface blockers, and develop the employee.
run-one-on-one
Use when preparing for or improving weekly one-on-one meetings between a manager and a direct report.
manager-as-coach
A management approach in which managers help people do their best work instead of only supervising them. It focuses on using strengths, removing obstacles, setting clear expectations, giving recognition, and keeping teams small.
team-scaling
Team Scaling & Engineering Organization: Designs engineering org structures, career ladders, hiring processes, and team topologies. Covers engineering levels, job descriptions, interview frameworks, org design patterns, team autonomy, and scaling from startup to enterprise. Use when the user mentions team scaling, org…
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.