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 modest-curator478/claude-skills --skill sales-leader-alignmentgit clone --depth 1 https://github.com/modest-curator478/claude-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/modest-curator478/claude-skills/sales-leader-alignment)<a href="https://agentmods.dev/skills/modest-curator478/claude-skills/sales-leader-alignment"><img src="https://agentmods.dev/badge/skills/modest-curator478/claude-skills/sales-leader-alignment/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/modest-curator478/claude-skills/sales-leader-alignment"><img src="https://agentmods.dev/badge/skills/modest-curator478/claude-skills/sales-leader-alignment.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.00233 | $0.02895 |
| Opus 5 | $0.00117 | $0.01448 |
| Sonnet 5 | $0.00047 | $0.00579 |
| Haiku 4.5 | $0.00023 | $0.00290 |
Grade A, and why
sales-leader-alignment 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-leader-alignment — 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 — 343 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sales Leader Alignment: Shifting a Skeptical or Adversarial Relationship
This skill addresses the most common and most politically damaging situation a demand gen or RevOps leader faces: a sales leader who does not believe marketing is adding value, will not prioritize marketing-sourced leads, and either actively undermines or passively ignores the programs marketing is building.
This is not a process problem. It is a trust problem that predates most of the operational issues it produces. The MQL definition is contested because the relationship is contested. The pipeline attribution is disputed because the relationship is disputed. Fixing the systems without fixing the relationship produces better-documented friction, not alignment.
This skill does not assume the sales leader is wrong. In many cases the skepticism is earned. Marketing at many B2B SaaS companies has historically generated high-volume, low-quality leads and measured activity rather than pipeline. A sales leader who has been burned by that is not being irrational. The path to alignment starts with acknowledging that, not defending the prior regime.
HOW TO SET UP THIS SKILL
Provide:
- What the sales leader has said or done that indicates the problem
- How long the dynamic has existed
- Whether you are new to the role or have been in it for some time
- What you have already tried
- Whether the sales leader reports to the same person you do, or is a peer versus a senior stakeholder
- The specific business context: stage of company, whether there is a shared revenue target, and whether leadership above both of you sees the problem
Diagnosing the Type of Misalignment
The approach differs based on what is actually driving the friction. Most sales-marketing misalignment falls into one of four types.
Type 1: Earned skepticism from prior marketing performance
The sales leader has legitimate reasons to distrust marketing based on historical experience. High lead volume with low conversion. Programs that generated activity metrics but no pipeline. Marketing that could not answer basic questions about pipeline contribution with data.
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 · 343 lines · 233 tokens per session scan A 1884a83e980d
sales-leader-alignment is a skill published in the GitHub repository modest-curator478/claude-skills (4 stars, last pushed today), licensed MIT. It adds 233 tokens to every session and 2,895 once invoked, about $0.0012 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to sales-leader-alignment, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
TEMPLATE
../../../agents/personas/TEMPLATE.md.
code-review
Pre-commit code review using code-reviewer agent for bug detection, security analysis, and quality assurance. Manual invocation only. Use before git commits to catch issues early. Blocks commits on REQUESTCHANGES verdict.
debug
Systematic debugging using error-detective and debugger agents instead of manual investigation. Triggers automatically on: error, bug, broken, failing, exception, stack trace, test failure. Orchestrates RCA-first approach with parallel agent investigation.
deep-context
Build deep codebase understanding using Capsule context, progressive-reader, and specialist agents instead of overwhelming main context. Triggers on: don't have context, understand codebase, learn about, need background. Implements progressive context building.
task-router
Decision matrix for choosing optimal approach to any task. Helps Claude decide when to delegate to sub-agents vs. working directly. Use when starting a new task or unsure of best approach.
workflow
Systematic task orchestration for complex multi-step tasks. Triggers automatically when detecting: complex task, multi-step work, coordinate, orchestrate, break down. Guides through Understand → Strategy → Plan → Execute → Verify phases for comprehensive systematic approach.