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 abm-on-metagit 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/abm-on-meta)<a href="https://agentmods.dev/skills/swan-gtm/gtm-skills/abm-on-meta"><img src="https://agentmods.dev/badge/skills/swan-gtm/gtm-skills/abm-on-meta/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/abm-on-meta"><img src="https://agentmods.dev/badge/skills/swan-gtm/gtm-skills/abm-on-meta.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.00043 | $0.02238 |
| Opus 5 | $0.00022 | $0.01119 |
| Sonnet 5 | $0.00009 | $0.00448 |
| Haiku 4.5 | $0.00004 | $0.00224 |
Grade A, and why
abm-on-meta 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.
How it starts
The opening of the file, as written. The whole thing — 132 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Scale B2B Qualified Pipeline on Meta
A step-by-step playbook for turning Meta Ads spend into qualified pipeline (SQLs) for B2B, not cheap lead volume. This is the end-to-end system written at full depth.
The core idea (read first)
Most B2B teams run a Meta campaign, get a pile of low-quality leads, decide "Meta doesn't work for B2B," and move their budget somewhere else. In almost every case the setup was the problem, not the campaign.
Meta is extremely good at finding exactly what you ask it to find. If you optimise for "Lead" and give it nothing else to go on, it does its job perfectly and brings you the cheapest form-fills it can. They are real leads, they just never turn into pipeline.
The whole game is to change what you are asking for. When you (1) give Meta the right data so it understands your actual ICP, and (2) feed back which leads become qualified pipeline, Meta learns to go and find more of those. It is the same optimisation engine, now working toward qualified pipeline instead of cheap volume.
Everything below is how you do that.
Step 1 - Map the market & build the audience targeting
Goal: give Meta a high-quality, matchable audience built from your real target market.
- Map your TAM. Tier every company Tier 1 -> Tier 4 by fit. Decide where you want to go.
- Pull the contacts at those companies. That is your Tier 1-4 contact list - this list is the audience targeting.
- Enrich the list. Raw B2B / work-email lists match badly on Meta. Enrich for personal email + mobile numbers to lift the match rate, or the custom audience lands too small to run. (Mobile advertiser IDs / MAIDs are a minor assist only - iOS App Tracking Transparency degraded them; personal email + mobile number do the heavy lifting.)
- Enrichment data: Contact Level.
- Enrich + auto-sync audiences into Meta: Clay / Freckle.
- Push the enriched list to Meta as a custom audience.
Why: Meta builds audiences from people (not company names), so you need the real contacts. Tiering tells you where budget goes first. Match rate decides how big and usable the audience is - work emails barely match, personal email + mobile number are what Meta actually matches on.
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 · 132 lines · 43 tokens per session scan A 1c8f360dc5ea
abm-on-meta is a skill published in the GitHub repository swan-gtm/gtm-skills (153 stars, last pushed 2d ago), licensed MIT. It adds 43 tokens to every session and 2,238 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
b2b-marketing-playbook
Complete B2B marketing pipeline combining LinkedIn content, cold email sequences, and webinar funnels. Designed for SaaS founders doing $0–$1M ARR who need predictable lead generation. By @WeiYipei.
abm-dev
Enrich B2B people and companies with abm.dev — verified work emails, LinkedIn profiles, firmographics, and AI research with a citation and confidence on every field. Use when the user needs contact data, company intelligence, email-finding, people search at target accounts, or CRM enrichment writeback.
bdr-enablement-generator
Generates account research briefs, personalized outreach sequences, persona-specific talk tracks, and objection handling frameworks for B2B SaaS BDR teams. Use when preparing BDR outreach for target accounts, building prospecting sequences, creating call scripts, developing objection responses, onboarding new BDRs, or…
competitive-battlecard-generator
Generates and maintains competitive battlecards from win/loss data, competitor intel, G2 reviews, and sales feedback. Use when building battlecards for a specific competitor, updating existing battlecards with new intel, preparing BDRs or AEs for competitive deals, analyzing win/loss patterns against a competitor, or…
marketing-ops-sop-generator
Generates standard operating procedures for B2B SaaS marketing operations: campaign naming conventions, UTM governance, tool administration, workflow QA, data hygiene, lead routing, and incident response playbooks. Use when setting up or auditing marketing ops processes, onboarding a new marketing ops hire…
abm-program-orchestrator
End-to-end ABM program design and orchestration for B2B SaaS mid-market and enterprise motions. Use when building a target account list, designing account tiering criteria, planning ABM channel orchestration, coordinating BDR outreach with marketing campaigns, defining ABM measurement frameworks, or running an ABM…