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 event4u-app/agent-config --skill expansion-playbookgit clone --depth 1 https://github.com/event4u-app/agent-configWrote 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/event4u-app/agent-config/expansion-playbook)<a href="https://agentmods.dev/skills/event4u-app/agent-config/expansion-playbook"><img src="https://agentmods.dev/badge/skills/event4u-app/agent-config/expansion-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/event4u-app/agent-config/expansion-playbook"><img src="https://agentmods.dev/badge/skills/event4u-app/agent-config/expansion-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.00047 | $0.02124 |
| Opus 5 | $0.00023 | $0.01062 |
| Sonnet 5 | $0.00009 | $0.00425 |
| Haiku 4.5 | $0.00005 | $0.00212 |
Grade A, and why
expansion-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 7d 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 — 180 lines — stays where its author put it; the contents beside it link to each section on GitHub.
expansion-playbook
When to use
- Net Revenue Retention plateaued and the team cannot name which expansion lever drives it — upsell, cross-sell, and seat-expansion get conflated under "NRR" and the moves are uniform when they should be lever-specific.
- An expansion play is firing on usage signals alone — accounts using more seats are treated as expansion targets without checking the upstream pain that earned the expansion.
- A new pricing or packaging change is live and the team needs to re-key the expansion triggers to the new shape before the old triggers misfire.
Do NOT use to save churning accounts (route to
churn-prevention), design days 0–30 onboarding (route to
onboarding-design), or build product-led seat-expansion loops
unattended by a human play (route to retention-loops).
Cognition cluster
- Mental model 18 — Pull vs. push. Expansion that the buyer
pulls (because pain or scope grew) compounds; expansion the
vendor pushes (because the quarter needs the number) corrodes
the relationship and inflates churn the next cycle. Pick the
trigger that signals pull. See
docs/contracts/mental-models.md§ 18. - Mental model 9 — Hypothesis-driven thinking. Each expansion
trigger is a hypothesis: "if signal X is true, the buyer will
accept expansion Y at price Z." Triggers without falsification
evidence are wishes; if a trigger has misfired three times, the
trigger is wrong, not the buyer. See
mental-models.md§ 9. - Mental model 3 — Pareto (80/20). ~20 % of accounts carry
~80 % of expansion potential. Uniform expansion outreach across
the book is noise; weighted outreach by pull-signal strength is
reasoning. See
mental-models.md§ 3. - Context-spine — product + customer-segment. Read the
product slot for which capabilities the segment can absorb
next (sequencing matters — a cross-sell into a feature the
segment cannot use yet inflates churn), and the
customer-segment slot for switch-event patterns that signal
organic scope expansion. See
context-spine.
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.
- 7d ago First seen · 180 lines · 47 tokens per session scan A 3cdb8489d7dd
expansion-playbook is a skill published in the GitHub repository event4u-app/agent-config (10 stars, last pushed today), licensed MIT. It adds 47 tokens to every session and 2,124 once invoked, about $0.0002 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
save-progress
Save current project task progress to local task state file for cross-session continuity. Use when the user asks to save progress, uses an equivalent localized trigger phrase, the session is interrupted, or the user wants to resume work later. Writes to .claude/project-task-state.json so next session can load it via…
same-set-reusable-flow-for-project-file-inventor
Reusable MetaKim file inventory classification flow. It helps separate durable sources, generated evidence, runtime mirrors, temporary state, and risky unknowns before cleanup or commit.
meta-theory
MetaKim executable governance dispatcher. It classifies the run, loads only needed references, preserves foundational capabilities and runtime-native abilities, routes owner + weapon + dependency + runtime + OS + verification, and closes only with evidence, intent acceptance, and writeback decision.
starreel-drama-production
Operating skill for any AI agent driving the StarReel short-drama production pipeline (script → rewrite → extract → portraits + sheets → storyboards → frames → video → voiceover → final cut) over MCP or REST. Covers the ordered workflow, the entry-point decision table (which channel each kind of customer material…
seedance-20
Generate and direct cinematic AI videos with Seedance 2.0 (ByteDance/Dreamina/Jimeng). Covers text-to-video, image-to-video, video-to-video, and reference-to-video workflows with @Tag asset references, multi-character scenes, audio design, and post-processing. Use when making AI video, writing Seedance prompts…
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.