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 varunk130/ai-gtm-skill-library --skill customer-advocacygit clone --depth 1 https://github.com/varunk130/ai-gtm-skill-libraryWrote 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/varunk130/ai-gtm-skill-library/customer-advocacy)<a href="https://agentmods.dev/skills/varunk130/ai-gtm-skill-library/customer-advocacy"><img src="https://agentmods.dev/badge/skills/varunk130/ai-gtm-skill-library/customer-advocacy/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/varunk130/ai-gtm-skill-library/customer-advocacy"><img src="https://agentmods.dev/badge/skills/varunk130/ai-gtm-skill-library/customer-advocacy.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.00070 | $0.01327 |
| Opus 5 | $0.00035 | $0.00664 |
| Sonnet 5 | $0.00014 | $0.00265 |
| Haiku 4.5 | $0.00007 | $0.00133 |
Grade A, and why
customer-advocacy 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 — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Customer Advocacy (AMPLIFY Framework)
Design a customer advocacy program that converts happy customers into a predictable supply of references, case studies, peer reviews, and community influence - and ties advocacy activity back to pipeline. AMPLIFY replaces ad-hoc "can you do a quote?" asks with a structured advocate pipeline and an attribution model that earns the program ongoing investment.
Core Principle
Advocacy is a supply chain, not a favor. Most advocacy programs starve sales of references because they rely on relationship taps instead of a managed pipeline. AMPLIFY treats advocates like inventory: sourced, qualified, activated, replenished, and attributed.
The AMPLIFY Framework
| Letter | Stage | The Question |
|---|---|---|
| A | Advocate Identification | Who qualifies, and how is the candidate pool sourced continuously? |
| M | Motion Design | Which advocacy motions are in scope (reference, case study, review, speaker, community)? |
| P | Program Mechanics | What's the recruitment, onboarding, and reward design? |
| L | Library & Inventory | How is the advocate inventory tracked, and what's the SLA for sales requests? |
| I | Influence-to-Revenue | How is advocacy activity attributed to pipeline and revenue? |
| F | Feedback Loop | How is fatigue managed and the candidate pool replenished? |
| Y | Yield Optimization | Which motions and segments produce the highest influence per ask? |
Advocate Qualification
Not every happy customer qualifies. A useful candidate has:
| Dimension | Signal |
|---|---|
| Outcome proof | Quantified business result (revenue, cost, time) |
| Stakeholder fit | Named champion willing and authorized to be public |
| Brand fit | Customer logo aligns with target ICP segments |
| Reciprocity readiness | Willing to participate in ≥ 1 motion per quarter |
| Health stability | Health score green; no active risk plays |
Advocacy Motion Catalog
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 · 118 lines · 70 tokens per session scan A f53ded8dd014
customer-advocacy is a skill published in the GitHub repository varunk130/ai-gtm-skill-library (6 stars, last pushed 1mo ago), licensed MIT. It adds 70 tokens to every session and 1,327 once invoked, about $0.0003 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
session-deep-dive
Deep qualitative analysis of high-signal sessions. Spawns subagents with v2 template, synthesizes patterns, compares against known findings. Use after /session-scan.
brainstorm
Brainstorm Elixir/Phoenix features — explore ideas, compare approaches, gather requirements. Use when vague idea, not sure how to approach, or want to discuss before plan.
elixir-idioms
OTP/BEAM patterns and Elixir idioms — GenServer, Supervisor, Task, Registry, pattern matching, with chains, pipes. Use when designing processes or debugging BEAM issues.
tidewave-integration
Tidewave MCP runtime tools — debugging, smoke testing, live state inspection, SQL queries, hex docs. Use when evaluating code in a running Phoenix app.
plugin-dev-workflow
Guide plugin development workflow — editing skills, agents, hooks, or eval framework in this repo. Use when modifying files in plugins/elixir-phoenix/, lab/eval/, or lab/autoresearch/. Ensures changes pass eval, lint, and tests before committing.
110-java-maven-best-practices
Use when you need to review, improve, or troubleshoot a Maven pom.xml file — including dependency management with BOMs, plugin configuration, version centralization, multi-module project structure, build profiles, or any situation where you want to align your Maven setup with industry best practices. This should…