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 Frontal-so/outbound-skills --skill outbound-triggers-6git clone --depth 1 https://github.com/Frontal-so/outbound-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/frontal-so/outbound-skills/outbound-triggers-6)<a href="https://agentmods.dev/skills/frontal-so/outbound-skills/outbound-triggers-6"><img src="https://agentmods.dev/badge/skills/frontal-so/outbound-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/frontal-so/outbound-skills/outbound-triggers-6"><img src="https://agentmods.dev/badge/skills/frontal-so/outbound-skills/outbound-triggers-6.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.00056 | $0.00772 |
| Opus 5 | $0.00028 | $0.00386 |
| Sonnet 5 | $0.00011 | $0.00154 |
| Haiku 4.5 | $0.00006 | $0.00077 |
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 9d 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.
This is a copy
86% identical to outbound-triggers-6 — 4 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 145 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.
- 9d ago First seen · 145 lines · 56 tokens per session scan A 405b04148930
outbound-triggers-6 is a skill published in the GitHub repository Frontal-so/outbound-skills (5 stars, last pushed 2mo ago), licensed MIT. It adds 56 tokens to every session and 772 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 86% identical to outbound-triggers-6, differing in 4 lines, and is treated as a copy.
Other skills, from other repositories
audience-icp-filter
Filter an existing audience or lead list against your ICP and split it into ready-to-sequence segments. Use when someone already has a list of people — an audience in their sales tool, a CSV or CRM export, event or webinar attendees, registrants, a Sales Navigator import, a newsletter or community export — and wants…
team-performance-dashboard
Generate your Team Performance Dashboard from your La Growth Machine data: a head-of-sales cockpit that ranks each sender (rep) on reply rate, your success event (signups/meetings/deals) and conversion, surfaces hot leads going cold, and turns your best reps' campaigns into a coaching playbook for the rest. Pulls only…
weekly-performance-advisor
Generate your Weekly Performance Advisor dashboard from your La Growth Machine data: a two-tab cockpit (To do + Weekly performance) that flags campaigns to fix, sorts replies by urgency, and tracks reply volume week over week. It pulls only YOUR live LGM data, scores each running campaign against baked 3-zone…
outreach-icp-finder
Find your PROVEN ideal customer profile from your own outreach data — who actually replies, accepts and shows interest — then find more like them. Reads La Growth Machine via its MCP, or a CSV export from any outreach tool (lemlist, Instantly, Smartlead, HeyReach, Apollo, Waalaxy…). Use when someone asks which job…
objection-analyzer
Find out which objections your outbound gets, how well your team handled them, and what to say next time. Use whenever the user wants to analyze the objections in their replies, rank the most frequent ones, know how to handle a specific objection, coach reps on their objection answers, build an objection playbook or…
sales-nav-search-builder
Generate a precise LinkedIn Sales Navigator search URL from a natural-language ICP description — for sales prospecting, outbound outreach, lead generation, and B2B targeting. Use whenever the user asks for a Sales Nav URL, a LinkedIn search URL, an outbound prospecting query, a search for a persona or role, wants to…