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 atl-btl-messaginggit 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/atl-btl-messaging)<a href="https://agentmods.dev/skills/swan-gtm/gtm-skills/atl-btl-messaging"><img src="https://agentmods.dev/badge/skills/swan-gtm/gtm-skills/atl-btl-messaging/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/atl-btl-messaging"><img src="https://agentmods.dev/badge/skills/swan-gtm/gtm-skills/atl-btl-messaging.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.00063 | $0.00813 |
| Opus 5.5 | $0.00025 | $0.00325 |
| Sonnet 5.5 | $0.00013 | $0.00163 |
| Haiku 4.5 | $0.00006 | $0.00081 |
Grade A, and why
atl-btl-messaging 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 1mo 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:
- atl-btl-messaging — 92% identical, 4 lines differ
How it starts
The opening of the file, as written. The whole thing — 137 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ATL vs BTL Messaging Framework
Above-the-Line (ATL) - VPs, C-Level, Directors
Mindset:
- Think past and future (strategic)
- Want validation, not problems solved
- Care about big picture, not daily operations
What They Care About:
- Revenue impact
- Risk reduction
- Strategic initiatives
- Competitive positioning
- Board/investor optics
Message Length: 2-3 sentences only
Language to Use:
- "Strategic initiative"
- "Revenue impact"
- "Competitive advantage"
- "Board-level priority"
- "Risk mitigation"
Example ATL Email:
Subject: Q1 revenue efficiency
{{firstName}},
If you could identify revenue leakage 3 months faster, what would that mean for next year's targets?
We helped {{similar_company}}'s CEO do exactly that.
15 minutes to explore?
Fatal ATL Mistake: Talking about operational problems = immediate delegation to subordinate
Below-the-Line (BTL) - Managers, ICs, End-Users
Mindset:
- Think present (tactical)
- Want problems solved immediately
- Care about daily workflow
What They Care About:
- Daily pain points
- Time savings
- Workflow improvements
- Making their job easier
- Looking good to their boss
Message Length: 3-4 sentences acceptable
Language to Use:
- "Stop spending 3 hours every week on..."
- "Eliminate the manual work of..."
- "Never deal with {{pain}} again"
- "Save {{X}} hours per week"
Example BTL Email:
Subject: 3 hours back
Hey {{firstName}},
Stop spending 3 hours every week fighting with Excel.
We helped {{similar_company}}'s ops team cut their reporting time by 70%.
Want to see how?
Fatal BTL Mistake: Talking about ROI and strategic impact = doesn't resonate, too abstract
Decision Framework: Who to Target
Target ATL (Executives) When:
- Deal size > $50K ACV
- Strategic/transformation purchase
- Requires budget approval from top
- Long sales cycle acceptable
Target BTL (End-Users) When:
- Product-led growth motion
- User adoption drives expansion
- Bottom-up sale
- Need internal champion first
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.
- 1mo ago First seen · 137 lines · 63 tokens per session scan A 06eb10a01eaf
atl-btl-messaging is a skill published in the GitHub repository swan-gtm/gtm-skills (220 stars, last pushed 7d ago), licensed MIT. It adds 63 tokens to every session and 813 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-08-30.
Other skills, from other repositories
cold-outreach
Use when writing a cold email or LinkedIn DM to a stranger and its cadence: first-touch copy under a word ceiling, 4-7 step bump sequences, per-inbox volume and warm-up limits, the compliant opt-out footer. NOT SPF/DKIM/DMARC setup (that is email-deliverability), NOT sourcing the list (that is lead-gen), NOT life…
linkedin-outreach
Use when running LinkedIn social selling as a repeatable motion — Sales Navigator saved searches and trigger alerts, weekly request budgets, fixing a low acceptance rate, turning profile views and post engagers into warm threads, logging every touch. NOT the note or DM copy (that is cold-outreach), NOT the deal after…
Cold Email Writer
Write personalized cold outreach emails to hiring managers and founders - specific, human, not a pitch deck.
afrexai-lead-hunter
Enterprise-grade B2B lead generation, enrichment, scoring, and outreach sequencing for AI agents. Find ideal prospects, enrich with verified data, score against your ICP, and generate personalized outreach — all autonomously.
agent-browser
Drive a real headless Chromium on the workspace host to read pages, fill forms, click buttons, run JS, and take screenshots. Use this whenever you need more than a plain HTTP fetch — pages that require JS to render, pages with an interactive element you have to click through, or when you want an accessibility-tree…
find-leads
Find qualified B2B leads with OpenOutreach — run openoutreach find N [emails], read the CSV it prints on stdout, and hand the rows to whatever sends. Use when the user wants leads, prospects, an ICP-matched contact list, or asks what a campaign already has. Also covers first-run setup (openoutreach init), openoutreach…