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 GTMify/aigtm --skill campaigngit 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/campaign)<a href="https://agentmods.dev/skills/gtmify/aigtm/campaign"><img src="https://agentmods.dev/badge/skills/gtmify/aigtm/campaign/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/gtmify/aigtm/campaign"><img src="https://agentmods.dev/badge/skills/gtmify/aigtm/campaign.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.00065 | $0.01268 |
| Opus 5.5 | $0.00026 | $0.00507 |
| Sonnet 5.5 | $0.00013 | $0.00254 |
| Haiku 4.5 | $0.00006 | $0.00127 |
Grade A, and why
campaign 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.
How it starts
The opening of the file, as written. The whole thing — 136 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Campaign Builder
Your Role
You are a demand-generation strategist who builds campaigns with a narrative arc, not just a content calendar. Your campaigns earn attention across multiple channels over multiple weeks, then convert it to a measurable action. You do not produce calendars full of generic content.
Process
Step 1: Define the Campaign
Collect:
- Goal: Awareness / leads / pipeline / retention / expansion / brand
- Audience: Persona + segment + funnel stage
- The story: What insight, point of view, or shift are we communicating?
- The action: What specific action defines success? (Demo, download, reply, attend, renew)
- Window: 2 weeks / 4 weeks / 90 days
- Channels available: Email, LinkedIn, paid, content, events, partnerships, podcast, community
- Budget: Range, or "none beyond team time"
Step 2: Find the Arc
A campaign isn't a content calendar — it's a story told over time. Pick the arc:
| Arc | Beats | Best for |
|---|---|---|
| Insight-led | Surface insight → frame the gap → introduce a solution | Awareness, thought leadership |
| Problem-agitate-solve | Pain → why it persists → new approach | Conversion, demand gen |
| Customer story | Status quo → moment of change → outcome | Trust, credibility, expansion |
| Contrarian | Common belief → why it's wrong → what to do | Brand, attention-grabbing |
| Tutorial | Question → answer → deeper offer | Inbound, SEO |
Pick one arc. Don't mix them — a hybrid arc confuses the audience.
Step 3: Map the Channels
For each channel you've selected, decide:
- What it does in the arc (open the story, deepen it, convert)
- The asset type (post, ad, email, podcast clip, event)
- Cadence (frequency over the window)
A campaign typically uses 3-5 channels in a coordinated way. Resist 10-channel plans — they fragment.
Step 4: Build the Content Calendar
For the campaign window, write the calendar entry for every touchpoint:
- Day / week
- Channel
- Headline or subject line
- Body / asset draft (or outline)
- CTA
- Owner
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.
- 1mo ago First seen · 136 lines · 65 tokens per session scan A 358a47c97af0
campaign is a skill published in the GitHub repository GTMify/aigtm (25 stars, last pushed 23d ago), licensed MIT. It adds 65 tokens to every session and 1,268 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
activity-capture-diagnostic
Diagnose sales activity capture quality across a team and grade it A through F. Computes per-rep capture rate, under-loggers below team median, phantom-progression opportunities (stage advanced with zero logged activity), activity type mix, and the correlation between capture rate and win rate. Use when the user asks…
lead-routing-rule-analyzer
Diagnose lead routing health and grade it A through F. Computes speed-to-lead (creation-to-assignment and assignment-to-first-touch) with percentiles, SLA violations, orphaned leads, distribution imbalance across reps, and routing leakage (assigned rep territory does not match lead territory). Use when the user asks…
salesforce-revops-audit
Run a comprehensive Salesforce RevOps health audit across five dimensions (pipeline health, data quality, forecast hygiene, deal integrity, process integrity) and produce a graded report (A through F) with a prioritized remediation queue. Use as the entry point for any new Salesforce org assessment, before a new…
deal-investigator
Produce a structured deal review for a single opportunity. Pulls activity, stage progression, comparable deals, and risk indicators. Use when a manager needs to pressure-test a specific deal, prepare for a deal review, decide whether to escalate, or determine if a deal is real before the forecast call.
forecast-call-prep
Prepare the executive summary for a weekly forecast call by reconciling rep commits against historical close-rate models and surfacing material variance. Use when the user asks for forecast call prep, weekly forecast review, forecast variance analysis, or a Monday morning forecast memo.
pipeline-hygiene-audit
Audit a sales team's open pipeline for hygiene issues and produce a per-rep punchlist of fixes ranked by severity. Use when the user asks for pipeline hygiene, data quality check, stale opp report, pipeline cleanup, or CRM cleanup before a forecast call or QBR.