agentmods.dev

sales-funnel-systems-auditor

sales-funnel-systems-auditor is a skill for Claude Code from jpeslar1/john-peslar-ai-skills. It costs 155 tokens per session (1,690 once invoked), scanned A, original, MIT.

A framework for examining founder-led sales systems, including lead generation, newsletters, webinars, communities, productized services, and software offers. It treats the sales funnel as the full path from attracting attention to delivery and referrals.

In plain words
What is it for?
Use it to map buyer stages, evaluate marketing and sales activities, find leaks in conversion and follow-up, and make the process more repeatable.
Why use it?
It reveals problems such as unclear offers, competing calls to action, weak follow-up, invisible pipeline status, and sales processes that depend on the founder's memory.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the lead-generation plugin — 5 skills shipped together

not rated 6repo +1 3d ago A scan 155 tokens original MIT

Good fit Use it to map buyer stages, evaluate marketing and sales activities, find leaks in conversion and follow-up, and make the process more repeatable.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/jpeslar1/john-peslar-ai-skills/sales-funnel-systems-auditor
View source ↗ jpeslar1/john-peslar-ai-skills
Install

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.

Any agent
npx skills add jpeslar1/john-peslar-ai-skills --skill sales-funnel-systems-auditor
Clone the repo
git clone --depth 1 https://github.com/jpeslar1/john-peslar-ai-skills

Made for: Claude Code.

Or install lead-generation, the plugin that ships this one along with the rest of its 5 skills.

Wrote 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.

agentmods badge for sales-funnel-systems-auditor

README.md
[![agentmods](https://agentmods.dev/badge/skills/jpeslar1/john-peslar-ai-skills/sales-funnel-systems-auditor/github.svg)](https://agentmods.dev/skills/jpeslar1/john-peslar-ai-skills/sales-funnel-systems-auditor)
Your own site
<a href="https://agentmods.dev/skills/jpeslar1/john-peslar-ai-skills/sales-funnel-systems-auditor"><img src="https://agentmods.dev/badge/skills/jpeslar1/john-peslar-ai-skills/sales-funnel-systems-auditor/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.

agentmods 80×15 button for sales-funnel-systems-auditor

Your own site · 80×15
<a href="https://agentmods.dev/skills/jpeslar1/john-peslar-ai-skills/sales-funnel-systems-auditor"><img src="https://agentmods.dev/badge/skills/jpeslar1/john-peslar-ai-skills/sales-funnel-systems-auditor.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 155 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,690 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00155 $0.01690
Opus 5 $0.00077 $0.00845
Sonnet 5 $0.00031 $0.00338
Haiku 4.5 $0.00015 $0.00169

Measured 12d ago against content hash 431f3ca9fcb8, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

sales-funnel-systems-auditor 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.

sales-funnel-systems-auditor/SKILL.md · 197 lines

How it starts

The opening of the file, as written. The whole thing — 197 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Sales Funnel Systems Auditor

Use this skill to diagnose a funnel as an operating system, not a pile of tactics. Focus on the path from attention to trust to conversion to delivery to referrals.

Core Principle

Most founder-led funnels do not have a traffic problem first. They have a sales-system problem:

  • The offer ladder is unclear.
  • Too many CTAs compete for the same buyer.
  • Nurture does not route by buyer state.
  • Pipeline truth is not visible.
  • Sales activity depends on the owner's memory, mood, and spare time.
  • Proof from delivery is not packaged back into acquisition.

The goal is to turn the funnel into a visible, measurable, repeatable system.

Audit Workflow

  1. Map the funnel

    • Top-of-funnel channels
    • Lead capture assets
    • Owned audience
    • Trust-building surfaces
    • Conversion events
    • Offers
    • Delivery experience
    • Upsells, referrals, reactivation

  2. Identify buyer states

    • Curious learner
    • Problem-aware lead
    • Ready-to-build operator
    • Ready-to-outsource buyer
    • Existing customer
    • Referral source

  3. Score the funnel Use a 1-10 score across:

    • Target market clarity
    • Message clarity
    • Media/channel fit
    • Lead capture
    • Nurture and segmentation
    • Conversion mechanism
    • Delivery experience
    • Lifetime value path
    • Referral system
    • Pipeline visibility

  4. Find the leaks Look especially for:

    • CTA overload
    • Traffic sent to the wrong offer
    • Lead magnets that do not imply the paid offer
    • Newsletter/community nurture with no clear ascension path
    • Webinars with weak follow-up
    • Launches without opens/clicks/replies/deposits tracked
    • Offers that mix DIY, DWY, and DFY without routing logic
    • Fake-full pipeline, stale leads, or no qualification criteria

  5. Design the routing matrix Every warm lead should have one obvious next step based on current state.

  6. Recommend the operating cadence Include weekly review, dashboard metrics, follow-up rules, proof capture, and referral prompts.

Read the full file on GitHub · 197 lines

Changes

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.

  1. 12d ago First seen · 197 lines · 155 tokens per session scan A 431f3ca9fcb8

Subscribe to this mod's changes

sales-funnel-systems-auditor is a skill published in the GitHub repository jpeslar1/john-peslar-ai-skills (6 stars, last pushed 3d ago), licensed MIT. It adds 155 tokens to every session and 1,690 once invoked, about $0.0008 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.

Analytics and metricsMarketing and SEO
Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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…

microsoft/ai-agents-for-beginners · 200 tokens

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…

vercel/next.js · 95 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens