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 liqiongyu/lenny_skills_plus --skill sales-compensationgit clone --depth 1 https://github.com/liqiongyu/lenny_skills_plusWrote 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/liqiongyu/lenny_skills_plus/sales-compensation)<a href="https://agentmods.dev/skills/liqiongyu/lenny_skills_plus/sales-compensation"><img src="https://agentmods.dev/badge/skills/liqiongyu/lenny_skills_plus/sales-compensation/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/liqiongyu/lenny_skills_plus/sales-compensation"><img src="https://agentmods.dev/badge/skills/liqiongyu/lenny_skills_plus/sales-compensation.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.00021 | $0.02408 |
| Opus 5 | $0.00010 | $0.01204 |
| Sonnet 5 | $0.00004 | $0.00482 |
| Haiku 4.5 | $0.00002 | $0.00241 |
Grade A, and why
sales-compensation 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 — 140 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sales Compensation
Scope
Covers
- Designing compensation plans for revenue roles (typically SDR/BDR, AE, AM/CSM with expansion)
- Setting OTE, base/variable mix, quota, and ramp
- Defining commission mechanics (crediting rules, accelerators, clawbacks, payout timing)
- Aligning incentives with long-term customer value (retention / NRR), not just bookings
- Producing rep-facing plan docs + admin rules so payouts are actually operable
When to use
- “Design a comp plan for our first AEs/SDRs.”
- “What should our OTE and base/variable split be?”
- “Set quotas and a ramp plan for new reps.”
- “Create accelerators + rules so reps don’t game discounting.”
- “Our reps close bad-fit deals that churn—align comp with retention/NRR.”
When NOT to use
- You need to hire, structure, or onboard an early sales team (use
building-sales-teamfor org design, scorecards, and ramp plans) - You need to improve pipeline quality, lead scoring, or qualification criteria (use
sales-qualification) - You need to negotiate a specific offer with an individual candidate (use
negotiating-offers) - You need legal/tax/HR advice, employment compliance guidance, or jurisdiction-specific plan language (use qualified professionals)
- You’re designing executive compensation or equity plans (different problem)
- You don’t yet have basic GTM foundations (ICP, pricing, what counts as a closed-won) — do that first, then return
- You want an overly complex “formula soup” plan that can’t be explained in one page or administered reliably
Inputs
Minimum required
- Company stage + GTM motion (inbound/outbound/PLG/enterprise) and primary sales roles
- What you sell + pricing model + typical ACV/ARR and sales cycle length
- Your economic constraints: gross margin, CAC payback target (or runway), budget for sales comp
- Target outcomes for the period (bookings/revenue/NRR) and the time horizon you care about (e.g., 90-day retention, annual renewals)
- Current baseline (if any): pipeline conversion, win rate, ramp time, churn/NRR
- Constraints: simplicity tolerance, payout timing preference, risk tolerance (for the company and for reps)
What ships with it
13 files 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.
- eval/eval_config.json 1.6 KB
- eval/SHOWCASE.md 6.2 KB
- eval/with_skill.md 34 KB
- eval/without_skill.md 24 KB
- README.md 1.5 KB
- references/CHECKLISTS.md 2.1 KB
- references/EXAMPLES.md 896 B
- references/INTAKE.md 2.6 KB
- references/RUBRIC.md 4.6 KB
- references/SOURCE_SUMMARY.md 1.1 KB
- references/TEMPLATES.md 4.1 KB
- references/WORKFLOW.md 3.9 KB
- skillpack.json 371 B
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 · 140 lines · 21 tokens per session scan A ef671cc49418
sales-compensation is a skill published in the GitHub repository liqiongyu/lenny_skills_plus (52 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 21 tokens to every session and 2,408 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-09-03.
Other skills, from other repositories
exec-weekly-agenda-generator
Synthesize the past week across meetings, chat, email, and calendar to generate a ranked list of 5-10 topics for the weekly leadership team meeting. Use when the user asks to prep for their leadership meeting, generate meeting topics, build the agenda, or says "prep me for Monday.".
persona-event-coordinator
Plan and manage events — scheduling, invitations, and logistics.
persona-project-manager
Coordinate projects — track tasks, schedule meetings, and share docs.
persona-team-lead
Lead a team — run standups, coordinate tasks, and communicate.
recipe-plan-weekly-schedule
Review your Google Calendar week, identify gaps, and add events to fill them.
recipe-review-overdue-tasks
Find Google Tasks that are past due and need attention.