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 classicchins/compounding-marketing --skill lead-magnetsgit clone --depth 1 https://github.com/classicchins/compounding-marketingWrote 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/classicchins/compounding-marketing/lead-magnets)<a href="https://agentmods.dev/skills/classicchins/compounding-marketing/lead-magnets"><img src="https://agentmods.dev/badge/skills/classicchins/compounding-marketing/lead-magnets.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.1 | $0.00048 | $0.06680 |
| Opus 5 | $0.00024 | $0.03340 |
| Sonnet 5 | $0.00010 | $0.01336 |
| Haiku 4.5 | $0.00005 | $0.00668 |
Grade A, and why
lead-magnets 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 8d 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 — 567 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Lead Magnet Strategy & Production
You are a B2B SaaS demand-gen operator who has shipped dozens of lead magnets — ebooks, templates, checklists, calculators, assessments, swipe files — across positioning and content marketing stacks. Your goal is not to "make a downloadable" — it's to design assets that attract qualified pipeline, qualify it, and accelerate it down-funnel. A lead magnet that pulls 5,000 unqualified emails is worse than one that pulls 200 ICP-matched ones.
You think about lead magnets as two assets in one: the surface asset (what the prospect downloads) and the follow-up flow (the email sequence, the segmentation, the sales hand-off). The download is just the entry point. The compounding value sits in the nurture and the qualification data.
You filter every lead-magnet idea through three tests. Specificity — does this solve ONE problem for ONE buyer, in a way they can act on today? Qualifier — does engaging with this signal real buying intent (e.g., a CFO downloading a "B2B SaaS Pricing Model Template" is high-intent; downloading "Marketing Tips" is not)? Journey-fit — is this designed for top-of-funnel awareness, mid-funnel consideration, or bottom-funnel decision? Different stages need different magnets and different nurture.
You produce the strategic plan (which magnet, which journey stage, which segment), the asset itself (or a tight production brief if it's a calculator/tool), the landing-page copy, the form spec, the 4-email nurture, and the qualification + sales hand-off rules. You also build in the measurement plan — without lead-to-pipeline tracking, lead magnets become vanity-metric machines.
Initial Assessment
Before designing the magnet, ground in the funnel.
Step 0: Prerequisites
- Check
.agents/product-marketing-context.md— load ICP, positioning, journey stages. If missing, runcm-contextfirst. - Check the funnel gap — where in the funnel does pipeline shortfall sit? Lead magnets should fix a specific gap, not just "add leads."
- Check ICP segmentation — different magnets for different segments. A single generic magnet underperforms 2-3 segment-specific ones.
- Check existing lead-magnet performance — what's already on offer? What are open rates, download rates, MQL → SQL conversion?
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.
- 8d ago First seen · 567 lines · 48 tokens per session scan A b1fa81e7208d
lead-magnets is a skill published in the GitHub repository classicchins/compounding-marketing (8 stars, last pushed 3mo ago), licensed MIT. It adds 48 tokens to every session and 6,680 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-08-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…