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 sanky369/vibe-building-skills --skill lead-magnetgit clone --depth 1 https://github.com/sanky369/vibe-building-skillsWrote 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/sanky369/vibe-building-skills/lead-magnet)<a href="https://agentmods.dev/skills/sanky369/vibe-building-skills/lead-magnet"><img src="https://agentmods.dev/badge/skills/sanky369/vibe-building-skills/lead-magnet/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/sanky369/vibe-building-skills/lead-magnet"><img src="https://agentmods.dev/badge/skills/sanky369/vibe-building-skills/lead-magnet.svg" alt="Reviewed on agentmods" width="80" 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.00131 | $0.01803 |
| Opus 5 | $0.00066 | $0.00901 |
| Sonnet 5 | $0.00026 | $0.00361 |
| Haiku 4.5 | $0.00013 | $0.00180 |
Grade A, and why
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 12d 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 — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Lead Magnet
Design and draft the free offer that turns strangers into subscribers. Governing principle: a lead magnet solves one specific problem fast, and the problem it solves must be the first step of the problem the paid offer solves — so consuming the magnet naturally creates demand for the product, instead of attracting freebie-hunters who will never buy.
When to use / when not to
- Use when building or fixing the top of an email funnel, or when list growth has stalled.
- If there's no clear positioning yet, run
skills/marketing/positioning-anglesfirst — the magnet's problem slice comes from the positioning claim. - The landing page that sells the magnet is
skills/marketing/direct-response-copy's job; the emails that deliver it and convert to paid areskills/marketing/email-sequences' job. Produce the spec + asset here, then hand off. - If the user wants a recurring free email (not a one-time asset), that's
skills/marketing/newsletter.
Intake
One batch; reuse artifacts from skills/marketing/orchestrator and skills/marketing/positioning-angles instead of re-asking:
- What paid offer should this magnet ultimately sell, and what problem does that offer solve?
- Who exactly is the ideal subscriber, and what's the most painful first step of that problem for them?
- What do you already have that could be repurposed (talks, docs, spreadsheets, processes, data)?
- Any delivery constraints — email platform, ability to host PDFs/video, willingness to maintain a tool?
Don't stall: with a known offer and audience, choose the problem slice yourself, state it as an assumption, and proceed.
Workflow
1. Pick the problem slice
Choose one narrow, urgent sub-problem of the paid offer's problem. Decision rules:
- Must be solvable in one sitting (the magnet's consumption, not a course of study).
- Must be upstream of the paid offer: solving it should surface the need the product fills ("audit reveals gaps → product fixes gaps").
- Reject slices that fully substitute for the paid offer (cannibalizes sales) and slices so broad any audience would want them (attracts the wrong list).
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.
- 12d ago First seen · 123 lines · 131 tokens per session scan A e2fb580c89df
lead-magnet is a skill published in the GitHub repository sanky369/vibe-building-skills (30 stars, last pushed 2mo ago), licensed MIT. It adds 131 tokens to every session and 1,803 once invoked, about $0.0007 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
api-tester
A tool for creating and checking API tests from the real API contract and implementation. An API is the agreed way that software sends requests and receives responses.
dep-auditor
A read-only audit of a project’s third-party packages for known security issues, version health, and license facts. It uses the versions actually selected by lockfiles, which record the exact packages installed, rather than relying only on version ranges.
skill-curator
A Chinese-language evaluator for deciding whether developer tools and agent resources are suitable for a curated collection. It checks real repositories, installation paths, activity, duplicates, and security boundaries using evidence.
git-workflow
A guide for handling Git repository work safely, including status checks, branches, commits, pushes, pull requests, and rebasing. Git is a version-control system that records code changes and coordinates work between developers.
zh-readme
A tool for writing README files in Chinese after first examining a software project. A README is the main guide visitors see when they open a code repository.
env-manager
An environment-variable manager for project settings stored outside the code, often in .env files. It checks variable definitions and usage while keeping secret values out of reports and terminal output.