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 spiralcrew-ou/profilespider-agent-skills --skill lead-list-segmentationgit clone --depth 1 https://github.com/spiralcrew-ou/profilespider-agent-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/spiralcrew-ou/profilespider-agent-skills/lead-list-segmentation)<a href="https://agentmods.dev/skills/spiralcrew-ou/profilespider-agent-skills/lead-list-segmentation"><img src="https://agentmods.dev/badge/skills/spiralcrew-ou/profilespider-agent-skills/lead-list-segmentation/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/spiralcrew-ou/profilespider-agent-skills/lead-list-segmentation"><img src="https://agentmods.dev/badge/skills/spiralcrew-ou/profilespider-agent-skills/lead-list-segmentation.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.00039 | $0.00409 |
| Opus 5.5 | $0.00016 | $0.00164 |
| Sonnet 5.5 | $0.00008 | $0.00082 |
| Haiku 4.5 | $0.00004 | $0.00041 |
Grade A, and why
lead-list-segmentation 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.
What it actually says
Lead List Segmentation
Purpose
Divide a lead list into useful commercial segments with criteria, size, and priority.
When to use this skill
- Splitting one list into messaging-ready segments
- Prioritizing where to spend outreach effort
- Tailoring campaigns per segment
- Reporting list composition to stakeholders
When not to use this skill
- The list has no fields to segment on
- You need per-record scoring (use Lead Qualification)
- The list is too small to segment meaningfully
Required inputs
- A lead list
Optional inputs
- Segmentation dimensions (industry, size, region, fit)
- A priority rule
- Target segment count
Rules
- Define explicit, non-overlapping criteria per segment.
- Report accurate segment sizes.
- Base segments on supplied fields only.
- Recommend treatment proportional to value.
- Make priorities consistent and justified.
Process
- Profile the list fields.
- Choose segmentation dimensions.
- Define segment criteria.
- Assign records and count sizes.
- Recommend treatment and priority.
Output format
Return one record per segment with the following fields:
- segment_name
- segment_criteria
- included_records
- segment_size
- recommended_treatment
- priority
Validation
- Confirm segment criteria do not overlap.
- Confirm sizes sum sensibly to the list.
- Confirm priorities follow the value logic.
Limitations
- Segment quality depends on field completeness.
- Static segments need refreshing as the list grows.
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.
- 2mo ago First seen · 81 lines · 39 tokens per session scan A 2b2297341bcc
lead-list-segmentation is a skill published in the GitHub repository spiralcrew-ou/profilespider-agent-skills (11 stars, last pushed 4mo ago), licensed MIT. It adds 39 tokens to every session and 409 once invoked, about $0.0002 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.
lead-list-segmentation compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| lead-list-segmentationspiralcrew-ou/profilespider-agent-skills | Skill | 11 | 4mo ago | MIT | A | 39 | Claude Code, Codex |
| squeeze-page-builderAffitor/affiliate-skills | Skill | 767 | 18d ago | MIT | A | 114 | Claude Code |
| deepline-ads-audiencesgetaero-io/gtm-eng-skills | Skill | 73 | yesterday | MIT | A | 133 | Claude Code, Codex |
| deepline-enginegetaero-io/gtm-eng-skills | Skill | 73 | yesterday | MIT | A | 43 | Claude Code, Codex |
| deepline-plays-reviewgetaero-io/gtm-eng-skills | Skill | 73 | yesterday | MIT | A | 121 | Codex |
| b2b-marketing-playbookGingiris-1031/gingiris-skills | Skill | 89 | 2d ago | MIT | A | 53 | Claude Code, Codex |
| deepline-crm-cleaninggetaero-io/gtm-eng-skills | Skill | 73 | yesterday | MIT | A | 73 | Claude Code, Codex |