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.
git clone --depth 1 https://github.com/revaya-ai/revaya-aios-workspace-templateWrote 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/commands/revaya-ai/revaya-aios-workspace-template/lead-magnet)<a href="https://agentmods.dev/commands/revaya-ai/revaya-aios-workspace-template/lead-magnet"><img src="https://agentmods.dev/badge/commands/revaya-ai/revaya-aios-workspace-template/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/commands/revaya-ai/revaya-aios-workspace-template/lead-magnet"><img src="https://agentmods.dev/badge/commands/revaya-ai/revaya-aios-workspace-template/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.00000 | $0.00766 |
| Opus 5 | $0.00000 | $0.00383 |
| Sonnet 5 | $0.00000 | $0.00153 |
| Haiku 4.5 | $0.00000 | $0.00077 |
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 11d 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 — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Lead Magnet
Lead magnet research, strategy, and creation agent. Three-phase workflow: research what's working → propose the right asset → draft it. Reads content-strategy.md and lead-magnets.md before doing anything.
Variables
request: $ARGUMENTS (optional — specific idea or focus, e.g., "AI readiness checklist", or leave blank to start from research)
Instructions
You are building a lead magnet for you. This is a three-phase process. Do not skip phases or rush to draft before strategy is approved.
Phase 1: Research
Step 1a: Check existing research
Look in outputs/content-engine/research/ for any existing briefs on lead magnets or competitor assets. If relevant research exists from the last 30 days, summarize it and proceed to Phase 2.
Step 1b: If no brief exists, dispatch research subagent Use the Agent tool to research:
- What lead magnet formats are performing in AI/consulting/solopreneur space right now
- Specific examples with evidence of performance (downloads, engagement, testimonials)
- Title patterns that work (how they're worded)
- CTA mechanics being used (comment word, DM link, landing page)
- Formats: PDF, checklist, calculator, template, quiz, short guide, video workshop
- What's oversaturated vs. what's missing
Save research to outputs/content-engine/research/YYYY-MM-DD-lead-magnet-research.md.
Phase 2: Strategy
Read both files before making any recommendations:
context/content-engine/content-strategy.md— positioning, ICP/IFP audiences, tier systemcontext/content-engine/lead-magnets.md— existing assets, audit decisions, roadmap
Recommend a specific lead magnet:
## Lead Magnet Recommendation
**Name:** [proposed title]
**Format:** [PDF / checklist / template / calculator / guide]
**Target audience:** [ICP / IFP / both — with description]
**Tier fit:** [how it fits the free-with-email-capture tier]
**Core problem it solves:** [one sentence]
**Distribution mechanic:** [comment CTA / featured section / DM / landing page]
**Success metric:** [# downloads / # email captures — what does good look like?]
**Why this one first:** [rationale based on research + current positioning]
**Estimated effort:** [low / medium / high to produce]
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.
- 11d ago First seen · 86 lines · 0 tokens per session scan A 5fafe18163c5
lead-magnet is a command published in the GitHub repository revaya-ai/revaya-aios-workspace-template (2 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 766 tokens. 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 commands, from other repositories
deps-audit
Audit project dependencies for vulnerabilities, outdated packages, license conflicts, and supply chain risks — then provide actionable remediation strategies.
README
Git workflow and quality assurance commands for the claude-skills repository.
merge-conflict-analysis
You are analyzing merge conflicts for PR #${{ pr-number }}.
dispatcher
Pick the next-best repo to work on across the portfolio — rank free repos, recommend one, claim its lease atomically, and route to the entry command.
growth-seo
SEO audit and optimization for organic search ranking.
wcag-audit
Accessibility audit based on WCAG 2.1/2.2 and the axe-core reference.