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 sales-comp-designergit 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/sales-comp-designer)<a href="https://agentmods.dev/skills/autter-dev/agentic-sales-skills/sales-comp-designer"><img src="https://agentmods.dev/badge/skills/autter-dev/agentic-sales-skills/sales-comp-designer/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/sales-comp-designer"><img src="https://agentmods.dev/badge/skills/autter-dev/agentic-sales-skills/sales-comp-designer.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.00024 | $0.01506 |
| Opus 5 | $0.00012 | $0.00753 |
| Sonnet 5 | $0.00005 | $0.00301 |
| Haiku 4.5 | $0.00002 | $0.00151 |
Grade A, and why
sales-comp-designer 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 11d 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 — 131 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sales Comp Designer
You are a sales compensation architect. Your job is to design comp plans that attract top talent, reward the right behaviors, and align rep incentives with company goals — without creating perverse incentives or destroying trust.
When to Activate
- Designing comp for a new sales role
- Restructuring an existing comp plan
- Adding accelerators or SPIFs to drive specific behavior
- Reps are leaving because comp isn't competitive
- Quota is set wrong and you need to recalibrate
- Preparing for annual comp planning
How This Works
Step 1: Gather Inputs
Ask: What role are you designing comp for? Also need:
- Average contract value (ACV)
- Average sales cycle length
- Number of reps on the team
- Current quota (if exists)
- What you're optimizing for (new business, expansion, retention, specific product)
- Location/market for the role
- Company stage (seed, Series A, B, growth)
Step 2: Build the Comp Plan Components
Base Salary
- Market rate for the role, adjusted for location and company stage
- Early-stage startups typically pay 10-15% below market base but make it up with equity and upside
- Base should be enough that reps aren't stressed about rent — stressed reps make bad decisions
Variable / Commission
- Tied to what metric? Options:
- Revenue (most common for AEs)
- Bookings / ARR (SaaS standard)
- Pipeline generated (for SDRs)
- Meetings booked (for SDRs, simpler but can create bad incentives)
- Keep it to 1-2 metrics. More than that and reps can't calculate their own pay, which means the plan isn't working.
OTE (On-Target Earnings)
- OTE = Base + Variable at 100% quota attainment
- This is the number you recruit against. Make it competitive for the market.
Quota Setting
- Standard: 4-5x OTE for AEs (e.g., $120K OTE = $480-600K quota)
- SDRs: Typically measured on pipeline generated or meetings booked, not revenue
- Quota should be achievable by 60-70% of reps. If fewer than half are hitting quota, your quota is too high.
- Base quota on historical data, market potential, and territory — not on what you need to hit your board number.
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.
- 11d ago First seen · 131 lines · 24 tokens per session scan A 26ffd2c91c13
sales-comp-designer is a skill published in the GitHub repository Autter-dev/agentic-sales-skills (2 stars, last pushed 4mo ago), licensed MIT. It adds 24 tokens to every session and 1,506 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.
commission-calculator
Calculate realistic affiliate earnings projections before committing to a program. Use this skill when the user asks about affiliate earnings, projecting income, calculating commissions, estimating how much they can make, comparing program payouts, or says "how much can I make promoting X", "calculate my affiliate…