lead-scoring

lead-scoring is a skill for Codex from san-npm/skills-ws. It costs 79 tokens per session (5,559 once invoked), scanned A, original, MIT.

A guide for scoring sales leads and accounts by two factors: how well they match the target customer and how strongly they show buying interest. A lead is a potential customer, and an account is a company that may buy.

In plain words
What is it for?
Use it to design or tune scoring in HubSpot, Salesforce, Marketo, or a data warehouse, set MQL and SQL thresholds, route leads to sales, and check scores against won and lost deals.
Why use it?
It helps sales teams decide whom to contact first without treating a score as a replacement for human qualification.

Skill for Codex

Written for Codex: agents/openai.yaml present.

Good fit Use it to design or tune scoring in HubSpot, Salesforce, Marketo, or a data warehouse, set MQL and SQL thresholds, route leads to sales, and check scores against won and lost deals.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/san-npm/skills-ws/lead-scoring
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 san-npm/skills-ws --skill lead-scoring
Clone the repo
git clone --depth 1 https://github.com/san-npm/skills-ws

Made for: Codex.

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 lead-scoring

README.md
[![agentmods](https://agentmods.dev/badge/skills/san-npm/skills-ws/lead-scoring/github.svg)](https://agentmods.dev/skills/san-npm/skills-ws/lead-scoring)
Your own site
<a href="https://agentmods.dev/skills/san-npm/skills-ws/lead-scoring"><img src="https://agentmods.dev/badge/skills/san-npm/skills-ws/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.

agentmods 80×15 button for lead-scoring

Your own site · 80×15
<a href="https://agentmods.dev/skills/san-npm/skills-ws/lead-scoring"><img src="https://agentmods.dev/badge/skills/san-npm/skills-ws/lead-scoring.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 79 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 5,559 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.00079 $0.05559
Opus 5.5 $0.00032 $0.02224
Sonnet 5.5 $0.00016 $0.01112
Haiku 4.5 $0.00008 $0.00556

Measured 2mo ago against content hash ce99f4e2ba91, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 2mo 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.

skills/lead-scoring/SKILL.md · 284 lines

How it starts

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

Lead Scoring

Quantify how likely a lead/account is to buy (fit) and how actively they show intent (engagement), then route the highest-probability records to sales. This skill covers the scoring math, qualification frameworks, CRM + warehouse implementation, calibration against real outcomes, and privacy/compliance.

For the broader lifecycle (stages, conversion-rate analysis, pipeline math) see the sibling sales-funnel skill. Use this skill for the scoring/qualification layer that feeds those stages.

Scoring prioritizes outreach; it does not replace human qualification. A high score means "call sooner," not "close the deal." Discovery (BANT/MEDDIC) confirms what the score predicted.

Scoring Model Design

Two-Axis Model

Score on two independent axes so a great-fit-but-cold account isn't confused with a poor-fit tire-kicker who clicks everything:

  1. Fit Score (0–100): how well they match your ICP (firmographic/demographic). Mostly static; changes on enrichment or job change.
  2. Engagement Score (0–100): how actively they show buying intent (behavioral). Time-sensitive; decays.

Both axes are hard-capped at 100. Compute raw points, then clamp:

fit        = min(100, sum(fit_points))
engagement = min(100, sum(engagement_points_after_decay_and_dedup))
total      = round(0.4 * fit + 0.6 * engagement)   # 0–100

The 40/60 weighting favors intent over fit — flip toward fit (e.g., 60/40) in long, committee-driven enterprise sales where firmographics predict more than clicks. Calibrate the weights against won/lost data (see Calibration); do not ship the default blindly.

Use a grade × score matrix, not a single number, for routing. Collapsing fit and engagement into one total hides the most important quadrant. Route on the 2x2 below and keep total only as a tiebreaker/sort key.

Low engagement (<40) High engagement (≥60)
High fit (≥60) Nurture, account-based ads (A2 / "right fit, not ready") Hot — alert AE, SLA timer (A1)
Low fit (<40) Disqualify / low-touch (D) Reroute or self-serve; investigate why low-fit is so active (could be a competitor, student, or job seeker)

Read the full file on GitHub · 284 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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. 2mo ago First seen · 284 lines · 79 tokens per session scan A ce99f4e2ba91

Subscribe to this mod's changes

lead-scoring is a skill published in the GitHub repository san-npm/skills-ws (4 stars, last pushed 1mo ago), licensed MIT. It adds 79 tokens to every session and 5,559 once invoked, about $0.0003 per session on Opus 5.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.

Related

lead-scoring compared with skills from other repositories

lead-scoring next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
lead-scoringsan-npm/skills-wsSkill41mo agoMITA79Codex
imagegenopenai/codexSkill133kyesterdayApache-2.0A113Codex
playwright-climicrosoft/playwrightSkill99kyesterdayApache-2.0A19Claude Code
local-ai-agentsmicrosoft/ai-agents-for-beginnersSkill79k4d agoMITA200Claude Code, Codex
systematic-debuggingobra/superpowersSkill313k3d agoMITA21Claude Code
next-cache-components-adoptionvercel/next.jsSkill143kyesterdayMITA95Claude Code
next-partial-prefetching-adoptionvercel/next.jsSkill143kyesterdayMITA103Claude Code