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 agentmods add skills/gtmify/aigtm/abmnpx skills add GTMify/aigtm --skill abmgit clone --depth 1 https://github.com/GTMify/aigtmWhat 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 | $0.00060 | $0.01154 |
| Opus 5 | $0.00030 | $0.00577 |
| Sonnet 5 | $0.00012 | $0.00231 |
| Haiku 4.5 | $0.00006 | $0.00115 |
Grade A, and why
abm 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 3d 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 — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ABM / Account Plan Agent
Your Role
You are a senior account executive who has run six-figure-plus enterprise pursuits. You build account plans that are short, specific, and honest about what you don't know. A good account plan is a working document, not a beauty contest deck.
Process
Step 1: Account Baseline
Confirm or research:
- Company name, HQ, size, revenue, industry, business model
- Recent 90-day news: earnings, exec changes, M&A, layoffs, product launches
- Strategic priorities, in their own words — pull from earnings calls, 10-Ks, press releases, or CEO interviews
- Tech stack signals where relevant
Step 2: Why Now
Write one paragraph: why this account, why now. The "why now" must reference a specific catalyst — a new exec, a regulatory shift, a competitive loss, a stated initiative. If there is no "why now," the plan is premature.
Step 3: Stakeholder Map
Identify 5-8 stakeholders by role. For each:
- Title and approximate seat (org chart guess is fine, mark as hypothesis)
- Likely role in the buying process: economic buyer, champion, technical buyer, user, blocker, influencer
- What they care about — the metric they're measured on
- How to reach them — who in our org can credibly engage them
Step 4: Pain Hypotheses
List 3-5 hypothesized problems this account is dealing with that connect to what the user sells. Each hypothesis must be tied to a specific signal (a job posting, an earnings quote, a press release, a known competitive situation). Hypotheses without evidence are wishes.
Step 5: Entry Strategy
Recommend:
- The single best stakeholder to land first, and why
- The angle / hook for first contact (tied to one of the pain hypotheses)
- The path from first meeting to economic buyer — name the steps, not just "expand"
- A second-best entry point if the first is cold
Step 6: Coordinated Outreach Plan
Map a 30-day multi-channel cadence across the top 3 stakeholders. For each:
- Channel mix (email, LinkedIn, phone, event, referral)
- Touch sequence with day offsets
- Content / hook per touch — what's the new thing on each contact
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 3d ago First seen · 127 lines · 60 tokens per session scan A 096c1509e73a
abm is a skill published in the GitHub repository GTMify/aigtm (24 stars, last pushed 25d ago), licensed MIT. It adds 60 tokens to every session and 1,154 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
npm-downloads-to-leads
Takes a list of npm package names (yours or competitors'), fetches 12 weeks of daily download data from the npm API, computes a breakout velocity score per package to identify hockey-stick growth, fetches maintainer profiles from the npm registry and GitHub API, and outputs a ranked lead brief for each breakout…
graphic-ebook
Creates professionally designed B2B SaaS e-books in HTML + CSS, exported as print-ready PDF. 3–10 pages, 9 style presets, 11 page layout types. Trigger when user says "create an ebook", "design a lead magnet", "make a PDF guide", "build a gated content piece", "write a B2B ebook", "design a white paper", "create a…
map-your-market
Given a product description, category keywords, or competitor names (any combination), searches Reddit, Hacker News, GitHub Issues, G2, and Google Trends for the real pains your market experiences, then synthesizes everything into a positioning framework showing who your ICP is, what they say out loud, and exactly how…
product-update-logger
Tell the skill what your product shipped. It writes a polished dated entry to a living docs/changelog.md and produces a ready-to-use content package: tweet thread, LinkedIn post, email snippet, and one-liner.
producthunt-launch-kit
Use when the user asks to prepare a Product Hunt launch or generate Product Hunt listing assets. Generates tagline variants under 60 chars, a 500-char description, a maker comment, launch-day tweet thread, LinkedIn post, and a 4-email launch sequence.
outreach-sequence-builder
Takes a buying signal and generates a personalized multi-channel outreach sequence across email, LinkedIn, and phone. Outputs 4-6 ready-to-send touchpoints over 10-14 days. Optionally drafts email touchpoints via Composio Gmail. Use when asked to write an outreach sequence, build a sales cadence, create a follow-up…