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 shawnpang/startup-founder-skills --skill lead-scoringgit clone --depth 1 https://github.com/shawnpang/startup-founder-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/shawnpang/startup-founder-skills/lead-scoring)<a href="https://agentmods.dev/skills/shawnpang/startup-founder-skills/lead-scoring"><img src="https://agentmods.dev/badge/skills/shawnpang/startup-founder-skills/lead-scoring/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/shawnpang/startup-founder-skills/lead-scoring"><img src="https://agentmods.dev/badge/skills/shawnpang/startup-founder-skills/lead-scoring.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.00060 | $0.01752 |
| Opus 5 | $0.00030 | $0.00876 |
| Sonnet 5 | $0.00012 | $0.00350 |
| Haiku 4.5 | $0.00006 | $0.00175 |
Grade A, and why
lead-scoring 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- lead-scoring — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Lead Scoring
When to Use
Activate when a founder needs to evaluate inbound prospects against ICP criteria, build a systematic qualification workflow, score and route leads, establish MQL/SQL definitions, or design pipeline stages. Also use when the user says "which leads should I focus on," "how do I qualify inbound leads," "define my ICP," "set up lead scoring," or "how do I route leads to the right person."
Context Required
From startup-context or the user:
- ICP definition — Who is the ideal customer (company size, industry, stage, geography, use case)
- Lead sources — Where inbound leads come from (website, events, content, referrals)
- CRM and tooling — Current stack for managing leads and deals
- Current customers — Who are the best existing customers and why
- Pipeline data — Existing deals, active customers, prior contacts
- Sales capacity — Who handles leads and what is their bandwidth
Work with whatever the user provides. If they have a clear problem area, start there. Do not block on missing inputs.
Workflow
- Load ICP and configuration — Read startup-context if available. Establish the qualification criteria across company attributes, person attributes, and use case fit.
- Parse the lead data — Accept leads in any format (CSV, list, CRM export, single name). Identify data gaps and flag what needs enrichment.
- Check pipeline overlap — Before scoring, check for existing customers (route to upsell), active deals (flag for sales coordination), and prior contacts (note history). Pipeline overlaps are routing flags, not disqualifiers.
- Score company fit — Evaluate against company size, industry, stage, geography, and use case alignment. Weight each dimension based on what predicts closed-won deals.
- Score person fit — Evaluate title, seniority, department, and decision-making authority. A perfect company with the wrong contact still needs routing, not rejection.
- Score use case alignment — Connect the lead's inferred intent to specific product capabilities. Inbound signals (demo requests, pricing page visits) tip borderline cases toward qualification.
- Generate composite score and verdict — Produce a 0-100 composite score and assign a routing recommendation.
- Export structured output — Deliver results in a table or CSV with all qualification data, scores, and routing.
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 · 111 lines · 60 tokens per session scan A cb6d88ce67dd
lead-scoring is a skill published in the GitHub repository shawnpang/startup-founder-skills (320 stars, last pushed 5mo ago), licensed MIT. It adds 60 tokens to every session and 1,752 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…