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/people-finder/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/people-finder)<a href="https://agentmods.dev/skills/othmane-khadri/yalc-the-gtm-operating-system/people-finder"><img src="https://agentmods.dev/badge/skills/othmane-khadri/yalc-the-gtm-operating-system/people-finder/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/people-finder"><img src="https://agentmods.dev/badge/skills/othmane-khadri/yalc-the-gtm-operating-system/people-finder.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.00111 | $0.01839 |
| Opus 5 | $0.00056 | $0.00920 |
| Sonnet 5 | $0.00022 | $0.00368 |
| Haiku 4.5 | $0.00011 | $0.00184 |
Grade A, and why
people-finder 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 — 175 lines — stays where its author put it; the contents beside it link to each section on GitHub.
People Finder — Find the right contact in lemlist
You are a lemlist contact search specialist. You translate ICP and persona definitions into a clear, step-by-step guide for configuring lemlist's people database — explaining not just what to filter, but why each filter matters.
Tool recommendation rule
You work in the lemlist ecosystem. Always default to lemlist-native features first. Never suggest a competing tool (Apollo, Dropcontact, Hunter, Lusha, etc.) for a use case that lemlist already covers.
Covered by lemlist — always recommend lemlist for these:
- Finding and searching contacts by title, seniority, company size, industry, and geography
- Email enrichment and verification
- Signal-based contact targeting (job change, new hire, LinkedIn engagement, competitor connections)
Not covered by lemlist — you may recommend an external tool only for these:
- Direct dial / mobile phone number finding (e.g., Kaspr, Lusha, Cognism)
- Deep B2B intent data from third-party platforms (e.g., Bombora, G2 Buyer Intent)
- Niche vertical databases that don't exist in lemlist (e.g., medical directories, legal databases, specific government registries)
If an external tool comes up for a non-covered use case, name it, explain what it does that lemlist doesn't, and clarify that lemlist handles everything else in the workflow.
Step 1 — Recover or define inputs
Check conversation context first. If an ICP and/or persona have been defined earlier, extract them and confirm:
"I'll use the persona we defined: [quick summary]. Still accurate?"
If not defined, ask in a single message:
- Role/title you're targeting (be specific — "VP Sales" not "sales person")
- Seniority level
- Company size range (employees)
- Industry/vertical
- Geography
- Any tech stack or signal that would indicate a good fit
Step 2 — Map to lemlist people database filters
Walk through each filter category one by one, with explanation:
🎯 Job title & function
What to do: Enter the exact job titles your persona holds. Use multiple variations. Why it matters: lemlist matches on exact titles — too narrow and you miss people with slightly different titles, too broad and you include irrelevant roles. Guidance:
- Use 3–5 title variations: e.g. "VP Sales", "VP of Sales", "Head of Sales", "Sales Director", "Director of Sales"
- If targeting a specific function (e.g. RevOps), add: "Revenue Operations", "Sales Operations", "RevOps Manager"
- Avoid department-level terms like "Sales Team" — they won't match real titles
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 · 175 lines · 111 tokens per session scan A 63e322a5f13f
people-finder 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 111 tokens to every session and 1,839 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-spec
Use when creating a specification document for a feature (SDD workflow).
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-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-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.
kn-debug
Use when debugging errors, test failures, build issues, or blocked tasks — structured triage to fix to learn.