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/zevenue/headless-gtm/creative-variablenpx skills add Zevenue/headless-gtm --skill creative-variablegit clone --depth 1 https://github.com/Zevenue/headless-gtmWrote 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/zevenue/headless-gtm/creative-variable)<a href="https://agentmods.dev/skills/zevenue/headless-gtm/creative-variable"><img src="https://agentmods.dev/badge/skills/zevenue/headless-gtm/creative-variable.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.00053 | $0.02482 |
| Opus 5 | $0.00026 | $0.01241 |
| Sonnet 5 | $0.00011 | $0.00496 |
| Haiku 4.5 | $0.00005 | $0.00248 |
Grade A, and why
creative-variable 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.
Creative Variable Discovery
You are Creative Variable Discovery - Zevenue's engine for identifying non-obvious personalization variables for an outbound campaign and specifying how to source them. You take a campaign angle + prospect profile and produce a variable spec (names, grammar, sources, extraction prompts, fallbacks, rendered examples).
The methodology is grounded in four recurring variable archetypes. The walkthrough in reference/worked-example.md shows the full pattern end-to-end.
What this skill produces vs. what you need infrastructure for
The skill always outputs a spec: variable names, grammar forms, sources, Claygent prompts, fallbacks, rendered examples. The spec is usable on day one regardless of what's wired up in Clay - it tells the team what to build, not what's already built.
Live extraction is optional and source-dependent:
- Free + Claude-Code-accessible (WebFetch + free public APIs): SEC EDGAR, UK Companies House, GitHub, Hacker News, Product Hunt, GDELT, PR Newswire RSS, SAM.gov, USPTO, OSHA, Form 990, company websites, public JDs, RSS feeds generally. The skill can pull these directly during the session to validate a variable on 5–20 prospects before you invest in a Clay pipeline. Treat this as ABM-tier preview, not production.
- Paid / scraper-required (Seeking Alpha, Tegus, G2, Glassdoor, SimilarWeb, Wappalyzer, ImportGenius, Phantombuster, Listen Notes, X API): the skill stops at the spec. Someone wires up Clay/n8n/Apify to actually extract at scale.
- Already wired in Clay (Apollo, Prospeo, TheirStack, Crunchbase, BuiltWith, Claygent): assume available. Skill produces the Claygent prompt; you paste it into the Clay column.
Tooling note: this skill assumes a Clay + Claygent stack because that's what we run. If you use a different stack, read "Claygent" as "any per-row LLM extraction step" and "Clay formula" as "any per-row deterministic transform." The spec format is stack-agnostic.
Order of operations: spec → Claude Code preview on 5 prospects (if source is free) → Clay pipeline (if preview works). Don't skip straight to Clay integration for a novel variable before proving it on a handful of real rows.
What ships with it
5 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 · 53 tokens per session scan A 2e6042cc23f8
creative-variable is a skill published in the GitHub repository Zevenue/headless-gtm (26 stars, last pushed 1mo ago), licensed MIT. It adds 53 tokens to every session and 2,482 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
a-b-testing
Design statistically sound GTM experiments for copy, channels, landing pages, sequencing, pricing, and funnel conversion. Produces hypothesis, sample-size logic, success metrics, test plan, analysis method, and scale/stop/kill recommendation. Use when planning A/B tests, split tests, or experiment roadmaps.
attribution
Build practical B2B attribution models across first touch, lead creation, opportunity creation, multi-touch, account-based influence, and sales-sourced revenue. Produces model comparison, UTM governance, source-of-truth rules, and channel ROI view. Use when marketing and sales disagree on source or ROI.
campaign-analytics
Analyze campaign performance from deliverability through revenue: delivery, engagement, replies, meetings, SQOs, pipeline, CAC, and payback. Produces diagnostic scorecard, root-cause analysis, benchmark comparison, and next-action plan. Use when deciding whether to scale, fix, or kill campaigns.
deliverability-monitoring
Monitor outbound deliverability health across domains, inboxes, DNS, bounces, spam placement, reply rates, and reputation signals. Produces alert thresholds, dashboard spec, weekly QA checklist, and remediation playbook. Use when inboxing drops, bounce rates rise, campaigns underperform, or new infrastructure launches.
tracking-plan
Master analytics tracking plan for PLG and B2B SaaS — unified event taxonomy, pixel strategy (1P and 3P tagging), marketing attribution architecture, CDP implementation (Segment, Rudderstack), product analytics (Amplitude, Mixpanel, PostHog), CRM tracking (HubSpot, Salesforce), and analytics infrastructure design. Use…
landing-page-copy
Landing page copywriting strategy — conversion copy frameworks, hero headline patterns, value proposition formulas, CTA copy, social proof placement, objection handling in copy, and A/B testing copy at scale. Based on Joanna Wiebe (Copyhackers), Oli Gardner (Unbounce), CXL (Peep Laja), and Harry Dry (Marketing…