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 swan-gtm/gtm-skills --skill outbound-triggers-6git clone --depth 1 https://github.com/swan-gtm/gtm-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/swan-gtm/gtm-skills/outbound-triggers-6)<a href="https://agentmods.dev/skills/swan-gtm/gtm-skills/outbound-triggers-6"><img src="https://agentmods.dev/badge/skills/swan-gtm/gtm-skills/outbound-triggers-6/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/swan-gtm/gtm-skills/outbound-triggers-6"><img src="https://agentmods.dev/badge/skills/swan-gtm/gtm-skills/outbound-triggers-6.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00062 | $0.00788 |
| Opus 5 | $0.00031 | $0.00394 |
| Sonnet 5 | $0.00012 | $0.00158 |
| Haiku 4.5 | $0.00006 | $0.00079 |
Grade A, and why
outbound-triggers-6 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- outbound-triggers-6 — 86% identical, 4 lines differ
How it starts
The opening of the file, as written. The whole thing — 147 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OUTBOUND Premises (6 Triggers)
1. CXO Passdown
Strategy: Start at the top, get passed down to the right person
Execution:
- Email C-level executive
- Ask for direction to right person
- Creates internal referral
Template:
{{firstName}},
I'm not sure if this lands on your desk or someone else's.
We help [ICP] with [problem].
Who should I be talking to about [topic] at {{company}}?
2. To "Groundswell" for Info
Strategy: Build internal champions before approaching decision maker
Execution:
- Target end-users and ICs
- Provide value and resources
- Build grassroots support
3. To "Groundswell" for Product-Placement
Strategy: Get product in hands of end-users first
Execution:
- Free trials to ICs
- Bottom-up adoption
- Let usage drive demand
4. To DM Based on "Groundswell" Product-Placement
Strategy: Use internal adoption as proof point for decision maker
Execution:
- Reference internal usage
- Show adoption metrics
- Convert to paid/enterprise
Template:
{{firstName}},
{{number}} people at {{company}} are already using [product].
[Names/teams] have been active for [timeframe].
Worth discussing how to scale this across the org?
5. Multi-Persona (Cross-Departmental)
Strategy: Coordinate outreach across multiple stakeholders
Execution:
- Map buying committee
- Tailor message per role
- Coordinate timing
Roles to target:
- Economic buyer (budget)
- Technical buyer (evaluation)
- End user (adoption)
- Champion (internal advocate)
6. Typical "Cold Outbound"
Strategy: Pure cold outreach with no prior signal
Execution:
- 1:1 personalization required
- Pattern-interrupt opening
- Heavy research investment
Messaging Approach:
First Line: Core-Static Relevance (Lean on Pattern Interruptive Opener)
Second Line: Core-Static Relevance ("We work with...")
Outbound Success Factors
- Deep research - Know the person and company
- Pattern interrupt - Stand out from generic emails
- Clear relevance - Why you, why now
- Multi-channel - Don't rely on email alone
- Persistence - Multiple touches required
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 · 147 lines · 62 tokens per session scan A 2829f1482b73
outbound-triggers-6 is a skill published in the GitHub repository swan-gtm/gtm-skills (150 stars, last pushed 2d ago), licensed MIT. It adds 62 tokens to every session and 788 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-30.
Other skills, from other repositories
signals-hooks
Comprehensive reactive state hooks for integration with flutterhooks.
signals-dart
Advanced reactive state primitives, collections, mixins, and utilities of signalscore.
signals-flutter
Highly optimized Flutter UI bindings and GPU rendering for reactive signals.
signals-migration-6-to-7
Detailed guidelines, patterns, and rules for migrating codebases from signals.dart version 6.x to version 7.x.
signals-preact-dart
Core reactive programming best practices and primitive definitions for preactsignals in Dart.
signals-lint
Standardized compiler diagnostics, static analysis lints, and automated IDE quick-fixes.