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 abm-playbookgit 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/abm-playbook)<a href="https://agentmods.dev/skills/varunk130/ai-gtm-skill-library/abm-playbook"><img src="https://agentmods.dev/badge/skills/varunk130/ai-gtm-skill-library/abm-playbook/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/abm-playbook"><img src="https://agentmods.dev/badge/skills/varunk130/ai-gtm-skill-library/abm-playbook.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.00096 | $0.01580 |
| Opus 5 | $0.00048 | $0.00790 |
| Sonnet 5 | $0.00019 | $0.00316 |
| Haiku 4.5 | $0.00010 | $0.00158 |
Grade A, and why
abm-playbook 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 — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ABM Playbook (TIER Framework)
Build a complete Account-Based Marketing playbook - tiered account list, buying-group map per tier, coordinated multi-channel plays, and pipeline acceleration plays for accounts already in cycle. ABM is structurally different from PLG, sales-led, and channel motions; this skill captures that difference rather than bolting it onto a generic GTM template.
Core Principle
ABM is a coordination problem, not a targeting problem. Most failed ABM programs pick the right accounts and then run the same demand-gen plays they always did. The TIER framework forces explicit coordination across channels and across tiers, with different play patterns for different account intimacy levels.
The TIER Framework
| Letter | Stage | The Question |
|---|---|---|
| T | Tier the Accounts | Which accounts get 1:1, which get 1:few, which get 1:many? |
| I | Identify the Buying Group | Who are the personas in each account, and what's each one's win condition? |
| E | Execute Coordinated Plays | What multi-channel plays run per account (not per persona)? |
| R | Re-route on Signal | When an account hits an in-cycle signal, which acceleration play activates? |
Account Tiering
| Tier | Account Count | Investment per Account | Personalization | Signal Cadence |
|---|---|---|---|---|
| 1:1 | 5-25 | High (custom content, exec engagement, dedicated SDR) | Per-account creative | Weekly |
| 1:few | 25-150 | Medium (cluster-level personalization, named SDR pod) | Per-cluster (3-8 accounts share) | Bi-weekly |
| 1:many | 150-2000 | Low (scaled programs with industry/persona personalization) | Per-segment creative | Monthly |
Buying Group Mapping
Every targeted account has a buying group, not a single buyer. The skill enforces explicit mapping:
| Role | Win Condition | Common Title Patterns |
|---|---|---|
| Champion | Personal outcome (career capital, problem solved) | Director / Sr. Manager in problem domain |
| Economic Buyer | Business outcome (revenue, cost, risk) | VP / SVP, CFO |
| Technical Evaluator | Risk reduction (architecture, security, fit) | Sr. Engineer / Architect / IT Director |
| End User | Day-to-day usability | Individual contributors |
| Procurement / Legal | Compliance, terms, pricing posture | Procurement, Legal, Security |
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 · 113 lines · 96 tokens per session scan A 1d2b08767814
abm-playbook is a skill published in the GitHub repository varunk130/ai-gtm-skill-library (6 stars, last pushed 1mo ago), licensed MIT. It adds 96 tokens to every session and 1,580 once invoked, about $0.0005 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…