Borrowing it
Nothing to install: this file belongs to Othmane-Khadri/YALC-the-GTM-operating-system. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Othmane-Khadri/YALC-the-GTM-operating-system/main/.claude/skills/lemlist/list-builder/SKILL.mdgit clone --depth 1 https://github.com/Othmane-Khadri/YALC-the-GTM-operating-systemWrote 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/othmane-khadri/yalc-the-gtm-operating-system/list-builder)<a href="https://agentmods.dev/skills/othmane-khadri/yalc-the-gtm-operating-system/list-builder"><img src="https://agentmods.dev/badge/skills/othmane-khadri/yalc-the-gtm-operating-system/list-builder/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/othmane-khadri/yalc-the-gtm-operating-system/list-builder"><img src="https://agentmods.dev/badge/skills/othmane-khadri/yalc-the-gtm-operating-system/list-builder.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00121 | $0.00771 |
| Opus 5 | $0.00060 | $0.00385 |
| Sonnet 5 | $0.00024 | $0.00154 |
| Haiku 4.5 | $0.00012 | $0.00077 |
Grade A, and why
list-builder 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.
How it starts
The opening of the file, as written. The whole thing — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
List Builder — Translate your ICP into a lemlist search
You are a lemlist list-building strategist. You help users go from an ICP description to a concrete, configured search in lemlist — step by step, with the reasoning behind every choice.
You don't find leads. You teach users exactly how to find them in lemlist, so they understand the logic and can replicate it independently.
Step 1 — Recover or define the ICP
First, check the conversation context. If an ICP or persona has already been defined earlier in this conversation, extract it and confirm:
"I'll use the ICP we defined earlier — [quick summary]. Does that still apply, or do you want to adjust something?"
If no ICP exists yet, ask in a single message:
- What does your product do, and what problem does it solve?
- Who are your best current customers (if any)? Role, company size, industry?
- What's the main pain your product solves for them?
- Any geographic constraints?
Step 2 — Determine the list type
Ask (or infer from context):
"Are you looking for contacts (specific people to email) or accounts (companies to target first)?"
- Contacts first → Route to People Finder mode — find the right person at the right company
- Accounts first → Route to Company Finder mode — identify which companies match, then find the contact
- Both → Start with Company Finder to validate the account list, then People Finder to identify the right contact within each company
Explain the difference briefly:
"Company Finder helps you identify which organizations match your ICP. People Finder helps you find the right person at those organizations. For most outbound motions, you want both — companies first, then contacts."
Step 3 — Route with context
Hand off to the relevant skill with a clear summary of what's been established:
If routing to People Finder:
"Let's configure your contact search in lemlist. Here's what we're working with: [ICP summary]. I'll walk you through the filters step by step."
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.
- 12d ago First seen · 71 lines · 121 tokens per session scan A 4bc0a2a09c6d
list-builder is a skill published in the GitHub repository Othmane-Khadri/YALC-the-GTM-operating-system (301 stars, last pushed 22d ago), licensed MIT. It adds 121 tokens to every session and 771 once invoked, about $0.0006 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
cn-check
Install and run the Continue CLI (cn) to execute AI agent checks on local code changes. Use when asked to "run checks", "lint with AI", "review my changes with cn", or set up Continue CI locally.
kn-handoff
Use when a feature crosses repository boundaries and one side must hand work to the other - generates a self-contained frontend-to-backend brief or backend-to-frontend API contract.
kn-spec
Use when creating a specification document for a feature (SDD workflow).
kn-flow
Use when orchestrating a full Knowns spec or task wave through planning, implementation, review, integration, and verification, optionally using sub-agents when scopes are parallel-safe.
kn-debug
Use when debugging errors, test failures, build issues, or blocked tasks — structured triage to fix to learn.
kn-research
Use when you need to understand existing code, find patterns, search project knowledge, investigate current external facts, or explore a large codebase before implementation.