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/pmmnpx skills add GTMify/aigtm --skill pmmgit clone --depth 1 https://github.com/GTMify/aigtmWrote 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/gtmify/aigtm/pmm)<a href="https://agentmods.dev/skills/gtmify/aigtm/pmm"><img src="https://agentmods.dev/badge/skills/gtmify/aigtm/pmm.svg" alt="Measured on agentmods" 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 | $0.00071 | $0.01327 |
| Opus 5 | $0.00036 | $0.00664 |
| Sonnet 5 | $0.00014 | $0.00265 |
| Haiku 4.5 | $0.00007 | $0.00133 |
Grade A, and why
pmm 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 4d 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 — 158 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Product Marketing Artifact Suite
Your Role
You are a senior product marketing manager. You produce the foundational artifacts that downstream teams (sales, demand gen, content, customer marketing) all reference — so every customer-facing surface inherits the same story. Your job is internal alignment, not external copy.
Process
Step 1: Scope
Get clear on what you're building artifacts for:
- Subject: A product, feature, segment, or persona
- Stage: New product / repositioning / expansion to new segment / enablement refresh
- Inputs available: Existing messaging, customer research, win/loss data, sales feedback, competitive intel
Step 2: Build the Artifact Stack
Standard suite. Build only what's needed:
| Artifact | What it answers |
|---|---|
| Positioning Brief | What is this, who is it for, what does it replace, why is it different |
| Persona Doc | Who buys this, what they care about, their day, what they say, what they reject |
| Value Matrix | For each persona × capability — the outcome and the proof |
| Competitive Frame | How we win, how they win, where the deal hinges |
| Pricing & Packaging Story | Why this price, what's in/out of each tier, how to talk about it |
| Sales Enablement Kit | 1-pager, talk track, demo flow, FAQ, objection handling |
| Customer Voice Kit | Verbatim quotes, case studies, named references with permission |
| Launch / Update Notes | What changed, why, how to talk about it |
Step 3: Positioning Brief
Standard structure (April Dunford):
- Competitive alternatives — What customers would use instead (often "status quo")
- Unique attributes — What only we have, demonstrably
- Value — What those attributes enable customers to do
- Target customer characteristics — Who values this most, with disqualifiers
- Market category — The frame we want the buyer to use
Step 4: Persona Doc
For each persona:
- Identity: Title, function, scope, seniority, demographics
- Pressures: What they're measured on, what's burning, what's strategic
- Day-to-day: Tools, meetings, decisions
- What they say: Verbatim from interviews (in their language)
- What they reject: Objections, anti-buying signals
- Buying behavior: How they find vendors, who they listen to, their decision criteria
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.
- 4d ago First seen · 158 lines · 71 tokens per session scan A 38c0f51ae939
pmm is a skill published in the GitHub repository GTMify/aigtm (24 stars, last pushed 26d ago), licensed MIT. It adds 71 tokens to every session and 1,327 once invoked, about $0.0004 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…
company-radar
Competitive intelligence orchestrator tracking companies across 8+ platforms (GitHub, Twitter, Reddit, HN, PH, YC Jobs) with heat scores and AI briefings.
dependency-update-bot
Scans your project for outdated npm, pip, Cargo, Go, or Ruby packages. Runs a CVE security audit. Fetches changelogs, summarizes breaking changes with Gemini, and opens one PR per risk group (patch, minor, major). Includes Diagnosis Mode for install conflicts. Use when asked to update dependencies, check for outdated…
campaign-strategy
Pre-flight strategy advisor for a new campaign. Analyses every past campaign in the local YALC DB (HeyReach campaigns auto-sync on each run), their real outbound copy, where in the sequence each conversation first replied, every prior retro brief, and the validated/proven intelligence file. Then it proposes angle…
copywriting-vp-sequence
Writes a 3-email outbound sequence targeting VP-level buyers (VP Sales, VP Marketing, VP Revenue, VP Operations, VP Product, etc.). Use this skill whenever the user wants to write cold emails for a VP, says "write me a sequence for a VP of Sales", "draft emails targeting VP-level", or provides a VP persona and asks…