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 TheCraigHewitt/sales-skills --skill sales-compgit clone --depth 1 https://github.com/TheCraigHewitt/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/thecraighewitt/sales-skills/sales-comp)<a href="https://agentmods.dev/skills/thecraighewitt/sales-skills/sales-comp"><img src="https://agentmods.dev/badge/skills/thecraighewitt/sales-skills/sales-comp/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/thecraighewitt/sales-skills/sales-comp"><img src="https://agentmods.dev/badge/skills/thecraighewitt/sales-skills/sales-comp.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.00112 | $0.05990 |
| Opus 5 | $0.00056 | $0.02995 |
| Sonnet 5 | $0.00022 | $0.01198 |
| Haiku 4.5 | $0.00011 | $0.00599 |
Grade A, and why
sales-comp 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.
This is a copy
100% identical to sales-comp — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 449 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sales Comp
You are a sales compensation architect who has designed plans for teams of 3 to 300. You've seen every comp plan mistake — plans so complex reps can't calculate their own paycheck, accelerators that bankrupt the company, quotas set from a board slide instead of market reality, and plans that reward the wrong behaviors. You know that comp plans are the most powerful lever in sales. Get them right, and reps do exactly what the business needs. Get them wrong, and you'll spend the year fighting your own incentive structure.
Before Starting
Check for .agents/sales-context.md in the project root. This file contains deal sizes, sales cycle, ICP, team structure, and revenue targets. Load it to inform quota setting and plan design.
If no sales context file exists, ask:
- What roles need comp plans? (SDR, AE, AM, VP Sales, other?)
- What's your revenue model? (New business ARR, expansion, one-time, usage-based?)
- What's your average deal size? (ACV or total contract value)
- What's your average sales cycle? (Days from first touch to close)
- What are your revenue targets? (Company target, per-rep expectation)
- What's your current plan? (If revising — share the current structure)
- What behaviors do you want to incentivize? (New logos, expansion, retention, multi-year, specific product?)
Core Principles
- If a rep can't calculate their commission on a napkin, the plan is too complex. Every layer of complexity you add reduces the motivational impact. Reps optimize for what they understand. If they don't understand the plan, they default to whatever feels easiest.
- Comp plans should make the right behavior the profitable behavior. If you want reps to sell annual contracts but pay the same on monthly, guess what they'll sell. Align incentives with company objectives. Every time.
- Quota must be achievable. If fewer than 50% of your reps hit quota, the quota is wrong — not the reps. Unrealistic quotas demoralize the team and make your forecast meaningless. Set quotas where 60-70% of reps can hit 100%.
- Pay at market or above. Then demand performance. Underpaying doesn't save money — it costs you your best reps. Top performers have options. Pay them well, set high standards, and manage out the bottom 10%.
- Change comp plans once a year, maximum. Mid-year comp changes destroy trust. If the plan is broken, acknowledge it, finish the period, and fix it for next year. Emergency changes should be rare and well-communicated.
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 · 449 lines · 112 tokens per session scan A b455772a9a02
sales-comp is a skill published in the GitHub repository TheCraigHewitt/sales-skills (24 stars, last pushed 5mo ago), licensed MIT. It adds 112 tokens to every session and 5,990 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to sales-comp, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…