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/cwinvestments/memstack/lead-magnetnpx skills add cwinvestments/memstack --skill lead-magnetgit clone --depth 1 https://github.com/cwinvestments/memstackWhat 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.00067 | $0.02804 |
| Opus 5 | $0.00034 | $0.01402 |
| Sonnet 5 | $0.00013 | $0.00561 |
| Haiku 4.5 | $0.00007 | $0.00280 |
Grade A, and why
memstack-marketing-lead-magnet 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 2d 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 — 337 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Lead Magnet — Creating lead capture asset...
Creates a lead magnet with format selection, content outline, landing page copy, email capture integration, delivery sequence, and nurture follow-up.
Activation
When this skill activates, output:
Lead Magnet — Creating lead capture asset...
Then execute the protocol below.
Context Guard
| Context | Status |
|---|---|
| User says "lead magnet", "opt-in", "freebie", "list building" | ACTIVE |
| User says "email list growth" or "grow my list" | ACTIVE |
| User wants to create a free asset to capture emails | ACTIVE |
| User wants a full sales funnel | DORMANT — use Sales Funnel |
| User wants paid ad copy | DORMANT — use Facebook Ad or Google Ad |
Common Mistakes
| Mistake | Why It's Wrong |
|---|---|
| "Give away your best stuff" | Your best stuff is the product. The lead magnet solves ONE specific problem to prove your expertise. |
| "Make a 50-page ebook" | Long ebooks have <10% completion rate. Short, actionable assets convert better. |
| "Any free thing works" | The lead magnet must directly relate to your paid offer. Unrelated freebies attract unqualified leads. |
| "No follow-up after delivery" | The lead magnet is the start of the relationship, not the end. Nurture with 3-5 emails minimum. |
| "Ask for too much info" | Every additional form field reduces conversions by 10-15%. Name + email is enough. |
Protocol
Step 1: Gather Requirements
If the user hasn't provided details, ask:
- Your paid product — what are you ultimately selling? (name, price, category)
- Target audience — who are you trying to attract? (role, pain point, skill level)
- Biggest problem — what's the #1 pain your audience has right now?
- Quick win — what small result can you deliver in <15 minutes?
- Distribution — how will you drive traffic? (ads, SEO, social, partnerships)
Step 2: Select Lead Magnet Type
Choose based on audience preference and production effort:
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.
- 2d ago First seen · 337 lines · 67 tokens per session scan A 03d521504b6a
memstack-marketing-lead-magnet is a skill published in the GitHub repository cwinvestments/memstack (417 stars, last pushed 5d ago), licensed MIT. It adds 67 tokens to every session and 2,804 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
plan-ceo-review
CEO/founder-mode plan review. Rethink the problem, find the 10-star product, challenge premises, expand scope when it creates a better product. Four modes: SCOPE EXPANSION (dream big), SELECTIVE EXPANSION (hold scope + cherry-pick expansions), HOLD SCOPE (maximum rigor), SCOPE REDUCTION (strip to essentials). Use when…
ship
Ship workflow: detect + merge base branch, run tests, review diff, bump VERSION, update CHANGELOG, commit, push, and create a PR. Use for an explicit /ship invocation or when the user requests the full ship, release, or deploy workflow. For an ordinary commit, push, or pull-request publishing request, use the built-in…
design-review
Designer's eye QA: finds visual inconsistency, spacing issues, hierarchy problems, AI slop patterns, and slow interactions — then fixes them. Iteratively fixes issues in source code, committing each fix atomically and re-verifying with before/after screenshots. For plan-mode design review (before implementation), use…
plan-eng-review
Eng manager-mode plan review. Lock in the execution plan — architecture, data flow, diagrams, edge cases, test coverage, performance. Walks through issues interactively with opinionated recommendations. Use when asked to "review the architecture", "engineering review", or "lock in the plan". Proactively suggest when…
pre-landing-review
Pre-landing PR review. Analyzes diff against the base branch for SQL safety, LLM trust boundary violations, conditional side effects, and other structural issues. Use when explicitly asked for the specialized pre-landing workflow. Product /review requests are handled by BitFun's unified Review mechanism instead.…
autoplan
Auto-review pipeline — reads the full CEO, design, eng, and DX review skills from disk and runs them sequentially with auto-decisions using 6 decision principles. Surfaces taste decisions (close approaches, borderline scope, codex disagreements) at a final approval gate. One command, fully reviewed plan out. Use when…