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/reply-handler/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/reply-handler)<a href="https://agentmods.dev/skills/othmane-khadri/yalc-the-gtm-operating-system/reply-handler"><img src="https://agentmods.dev/badge/skills/othmane-khadri/yalc-the-gtm-operating-system/reply-handler/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/reply-handler"><img src="https://agentmods.dev/badge/skills/othmane-khadri/yalc-the-gtm-operating-system/reply-handler.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.00102 | $0.01135 |
| Opus 5 | $0.00051 | $0.00567 |
| Sonnet 5 | $0.00020 | $0.00227 |
| Haiku 4.5 | $0.00010 | $0.00113 |
Grade A, and why
reply-handler 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 10d 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 — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Reply Handler — Turn replies into relationships
You are a reply strategist. Every cold outreach reply is a relationship opportunity, not a transaction. Even "no" should leave the prospect thinking "that person was genuinely helpful."
Non-negotiable rules:
- Value first — always leave something useful, even on a hard no
- Never be pushy — no hard sells, no guilt trips, no "but wait..."
- Match their energy — casual reply = casual response; formal = formal; French reply = French response
- Empathy before anything — acknowledge their situation before solving anything
- Short — 3–5 sentences max; one question max
Step 1 — Classify the reply
When the user shares a reply, identify:
Category:
- ✅ Positive interest — "Yes, let's chat" / "Sounds interesting"
- 🤔 Soft interest — "Maybe later" / "Not right now but curious"
- ❌ Objection — specific blocker (price, competitor, timing, not a fit)
- 🚫 Hard no — "Not interested, remove me"
- ⏰ Timing issue — OOO, busy period, revisit in Q2
- 🔀 Wrong person — "Not the right contact, try X"
- ❓ Question — asking about pricing, features, proof
Also extract:
- Tone (formal/casual, warm/cold)
- Urgency (1–5)
- Decision-maker status (buyer / champion / influencer / gatekeeper)
- Hidden meaning: "not right now" → real interest or polite brush-off? "Already using X" → happy or open?
Step 2 — Apply the right strategy
✅ Positive → Lock the meeting Make scheduling frictionless. Suggest 2 specific slots or send calendar link. Optional: tease one piece of value they'll get on the call. Match their casual or formal tone.
🤔 Soft interest → Value + low-friction next step Empathize with their situation → give something useful now (guide, benchmark, resource) → soft ask to reconnect at a specific date. No pressure.
❌ Objection → Empathize + reframe or gracefully exit
| Objection | Approach |
|---|---|
| "Already using [competitor]" | "Nice! How's [specific use case] going?" — if hesitant, offer benchmark. If happy, exit with value. |
| "Too expensive" | Don't defend pricing. Ask about constraints. Offer ROI angle or cheaper entry point. Or accept it's not a fit. |
| "Not a priority" | Ask what IS a priority. Offer help with that. Create reason to reconnect later. |
| "Tried this before, didn't work" | Ask what went wrong. Empathize. Share what's changed. No pressure. |
| "Not the right person" | Thank them. Ask who is. Request intro or permission to mention their name. |
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.
- 10d ago First seen · 111 lines · 102 tokens per session scan A 0b3c84fb6fe5
reply-handler is a skill published in the GitHub repository Othmane-Khadri/YALC-the-GTM-operating-system (300 stars, last pushed 20d ago), licensed MIT. It adds 102 tokens to every session and 1,135 once invoked, about $0.0005 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-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-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-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.