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 trigger-cadencegit 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/trigger-cadence)<a href="https://agentmods.dev/skills/varunk130/ai-gtm-skill-library/trigger-cadence"><img src="https://agentmods.dev/badge/skills/varunk130/ai-gtm-skill-library/trigger-cadence/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/trigger-cadence"><img src="https://agentmods.dev/badge/skills/varunk130/ai-gtm-skill-library/trigger-cadence.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.00081 | $0.00800 |
| Opus 5.5 | $0.00032 | $0.00320 |
| Sonnet 5.5 | $0.00016 | $0.00160 |
| Haiku 4.5 | $0.00008 | $0.00080 |
Grade A, and why
trigger-cadence 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 26d 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 — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Trigger Cadence (SPARK Framework)
Persona-only sequences send the same five emails to everyone who matches a title. Trigger Cadence starts from why this account might buy now, routes each trigger to its own cadence, and makes every touch reference the trigger so the outreach reads as timely rather than templated.
Core Principle
No trigger, no sequence. An account without a current reason to talk goes to nurture, not to a rep's inbox queue.
The SPARK Framework
| Letter | Step | The Question |
|---|---|---|
| S | Signal | What changed at the account in the last 30 days? |
| P | Point of view | What does that change likely break or unlock for them? |
| A | Ask | What is the smallest useful next step (a teardown, a benchmark, 15 minutes)? |
| R | Route | Which cadence fits this trigger's urgency and buyer? |
| K | Keep-warm rule | When does the sequence pause and hand the account to nurture? |
Trigger Routing Table
| Trigger | Buyer | Cadence | Touches / days |
|---|---|---|---|
| New funding | Founder / VP | Fast: email, LinkedIn, email, call | 4 / 10 |
| Hiring for the role you replace or support | Hiring manager | Medium: email, email, LinkedIn, email | 4 / 14 |
| Tech stack change | Technical owner | Medium: email with teardown, follow-up, call | 3 / 12 |
| New executive | New leader | Slow: congrats + POV, value asset, ask | 3 / 21 |
| Product usage spike (PLG) | Active user, then admin | Fast: in-app, email, call | 3 / 7 |
Process
- Detect - pull triggers from signal sources; discard any older than 30 days
- Write the POV - one sentence per account linking the trigger to a specific consequence
- Route - pick the cadence from the table; one active sequence per account at a time
- Draft touches - every touch names the trigger or its consequence; no touch without new value
- Set the keep-warm rule - no reply after the last touch, or trigger resolved → nurture for 60 days
- Review - sample 10 drafts; any that would make sense sent to a different account get rewritten
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.
- 26d ago First seen · 64 lines · 81 tokens per session scan A 45d56de6c68d
trigger-cadence is a skill published in the GitHub repository varunk130/ai-gtm-skill-library (7 stars, last pushed 12d ago), licensed MIT. It adds 81 tokens to every session and 800 once invoked, about $0.0003 per session on Opus 5.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-20.
Other skills, from other repositories
customer-journey-map
Construye un mapa de recorrido del cliente para un producto, servicio o experiencia. Úsalo cuando se te pida mapear un recorrido del cliente, crear un viaje del usuario, documentar puntos de contacto y puntos de fricción, o diseñar un mapa de experiencia. Produce un mapa de recorrido completo con etapas, puntos de…
design-handoff-brief
Transform feature briefs into structured design briefs that give designers the context they need before opening Figma. Use when asked to write a design brief, create a design handoff, brief a designer on a new feature, or translate a PRD into design requirements. Produces a brief with user goal, emotional context…
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.
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.