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/import-leads/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/import-leads)<a href="https://agentmods.dev/skills/othmane-khadri/yalc-the-gtm-operating-system/import-leads"><img src="https://agentmods.dev/badge/skills/othmane-khadri/yalc-the-gtm-operating-system/import-leads/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/import-leads"><img src="https://agentmods.dev/badge/skills/othmane-khadri/yalc-the-gtm-operating-system/import-leads.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Privilege Escalation · line 36 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- medium MCP Rug Pull · line 37 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
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.00084 | $0.00498 |
| Opus 5 | $0.00042 | $0.00249 |
| Sonnet 5 | $0.00017 | $0.00100 |
| Haiku 4.5 | $0.00008 | $0.00050 |
Grade A, and why
import-leads 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.
What it actually says
Import Leads
I'll wrap leads:import. Take an input file or Notion DB id, run the import, and surface the result-set id.
When This Skill Applies
- "just import this CSV"
- "load these leads without qualifying"
- "bulk import this file"
- "add these prospects to the DB"
- "pull this Notion DB into YALC"
NOT this skill (use qualify-leads instead):
- "qualify these leads" / "score this list" — that runs the 7-gate pipeline. This skill is import only.
NOT this skill (use scrape-post-engagers instead):
- "scrape engagers off this LinkedIn post" — that produces a result set from Unipile, not from a file.
Workflow
Step 0 — Ask for input source + path
"What's the input source — CSV, JSON, or Notion DB? And what's the path or DB id?"
Step 1 — Validate (file exists / Notion id format)
Step 2 — Shell out
cd ~/Desktop/gtm-os && set -a && source .env.local && set +a && \
npx tsx src/cli/index.ts leads:import --source <type> --input <path>
Step 3 — Parse output
CLI emits row count + result-set id.
Step 4 — Render
Step 5 — Offer follow-ups
"Want me to (a) qualify these via
qualify-leads --result-set <id>, (b) launch a campaign on the imported leads?"
Notes
- CSV expected columns: at least one of
email,linkedin_url. Other columns are kept as custom fields. - Notion DB requires a 32-char hex id. The CLI introspects schema and maps obvious columns.
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.
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 · 54 lines · 84 tokens per session scan A e97512ec68d4
import-leads 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 84 tokens to every session and 498 once invoked, about $0.0004 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
deepline-engine
Build, publish, and verify a Deepline Play as a durable state machine over Customer DB tables, including a small paid pilot. Invoke this skill explicitly when the user asks to build an engine.
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.
x-osv
CLI for Google OSV database. Query vulnerabilities for packages, scan local projects for vulnerable dependencies. Dependency: This is an x-cmd module. Install x-cmd first (see x-cmd skill). Required Tool: Install osv-scanner for project scanning (see https://github.com/google/osv-scanner).
obsidian-bases
Create and edit Obsidian Bases (.base files) with views, filters, formulas, and summaries. Use when working with .base files, creating database-like views of notes, or when the user mentions Bases, table views, card views, filters, or formulas in Obsidian.
vector-db
Vector database expert for embeddings, similarity search, RAG patterns, and indexing strategies.
elasticsearch
Elasticsearch expert for queries, mappings, aggregations, index management, and cluster operations.