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/cbrock84/headcount/lead-capturenpx skills add cbrock84/headcount --skill lead-capturegit clone --depth 1 https://github.com/cbrock84/headcountWhat 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.00069 | $0.00545 |
| Opus 5 | $0.00034 | $0.00272 |
| Sonnet 5 | $0.00014 | $0.00109 |
| Haiku 4.5 | $0.00007 | $0.00055 |
Grade A, and why
lead-capture 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 3d 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 — 55 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Lead capture
What gating costs
Every gate trades reach for contacts. That trade is worth making only when the contact is genuinely worth more than the reader — which is true far less often than it is assumed.
Gate: things with immediate practical utility that a buyer would use during evaluation — templates, calculators, assessments, data. Do not gate: thought leadership, anything you want cited or shared, or anything a competitor publishes openly.
Lead magnets
The test is whether someone would pay a small amount for it. If not, it will not earn an email address that gets used.
The best ones are things people use rather than read: a template that saves an afternoon, a calculator that answers a specific question, a checklist for a process they are mid-way through. An ebook that restates blog posts is not one.
Match the magnet to a stage. Someone downloading a beginner's guide is not ready for a sales call, and treating them as if they are burns the list.
Free tools
The strongest form: durable, earns links, and qualifies by use rather than by claim.
Build one only if it does something genuinely useful standalone, and keep the gate light — let people use it, and ask for the email to save or export the result. Gating before value is delivered converts a fraction as well.
Popups and overlays
Popups work and are widely hated; both facts matter.
- Trigger on behavior, not time — exit intent, scroll depth, or a second visit. A popup at three seconds interrupts someone who has not yet decided whether to care.
- Once per visitor, remembered. Repeated interruption is what generates the hatred.
- Never on mobile mid-content. Beyond the user cost, it is penalized.
- Offer something specific. "Subscribe to our newsletter" is not an offer. "The pricing calculator" is.
- One clear dismissal. Hidden or tiny close buttons cost more in reputation than they gain in conversions.
Forms
Every field costs conversion. Ask for what you need to do the next step and nothing for a later one — enrichment can fill the rest. Explain any field whose purpose is not obvious, since unexplained fields are where people abandon.
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.
- 3d ago First seen · 55 lines · 69 tokens per session scan A e2044ccaeb85
lead-capture is a skill published in the GitHub repository cbrock84/headcount (578 stars, last pushed 4d ago), licensed MIT. It adds 69 tokens to every session and 545 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
ideogram-ultra
Build Ideogram 4 (Ideogram Ultra) txt2img and img2img workflows with the local open-weights model, dual conditional/unconditional models with DualModelGuider, Qwen3-VL text encoder, and structured JSON ("compositional deconstruction") prompts for strong text rendering and layout control.
panel-node-pack-sync
Keep the ComfyUI sidebar panel node-pack (comfyui-agent-panel) in step with the orchestrator after comfyui-mcp updates. Use this whenever the orchestrator was just updated (installcomfyui (action:"selfupdate"), npm i -g comfyui-mcp, a new version in the ENVIRONMENT line), when a panel/bridge command fails in a way…
civitai
Discover Civitai models with the BUILT-IN downloadmodel action:"searchcivitai" and install/generate them locally. Find a checkpoint/LoRA/embedding on Civitai, download it into ComfyUI, and use its trigger words. Optionally pair the official Civitai MCP for community features (images browsing, posting, collections).
20-client-intake-brief-global
Use when an agency or freelancer takes on a NEW client and needs everything up front — an 11-section intake covering business overview, audience, current marketing, goals, budget, timeline, brand assets, approval process, and success criteria, written for the client to fill in and return. Trigger on 'client intake'…
aeo-geo
Strategy module for Answer Engine / Generative Engine Optimization — audits AI visibility, restructures content for citation, runs entity-consistency checks across Knowledge Graph, Wikidata, Wikipedia, Crunchbase, and LinkedIn, and produces JSON-LD schema specs, monitoring frameworks, and a 90-day LLM content…
spring-security-jwt
Use when an application issues and validates its own first-party JWT access and refresh tokens, including authentication filters, password encoding, RBAC, and method security. For JWTs issued by Keycloak, Auth0, Okta, Cognito, or another authorization server, use oauth2-resource-server.