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 modest-curator478/claude-skills --skill recruiter-outreachgit clone --depth 1 https://github.com/modest-curator478/claude-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/modest-curator478/claude-skills/recruiter-outreach)<a href="https://agentmods.dev/skills/modest-curator478/claude-skills/recruiter-outreach"><img src="https://agentmods.dev/badge/skills/modest-curator478/claude-skills/recruiter-outreach/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/modest-curator478/claude-skills/recruiter-outreach"><img src="https://agentmods.dev/badge/skills/modest-curator478/claude-skills/recruiter-outreach.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.00199 | $0.02523 |
| Opus 5 | $0.00100 | $0.01262 |
| Sonnet 5 | $0.00040 | $0.00505 |
| Haiku 4.5 | $0.00020 | $0.00252 |
Grade A, and why
recruiter-outreach 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.
This is a copy
100% identical to recruiter-outreach — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 330 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Recruiter Outreach: Short-Form Messages That Get a Response
This skill writes outreach messages for a senior B2B practitioner targeting Director-level demand gen, growth, or RevOps roles. The message types covered are: cold LinkedIn outreach to a recruiter who posted a role, warm outreach to a recruiter you have spoken with before, direct outreach to a hiring manager, and re-engagement of a dormant contact at a target company.
These are not cover letters. They are short, specific messages that demonstrate immediate fit and create a reason to respond. Most outreach at this level fails because it is too long, too generic, or opens with the candidate's needs rather than the reader's problem.
HOW TO SET UP THIS SKILL
Provide:
- The type of outreach: cold recruiter, warm recruiter, hiring manager, or dormant contact reactivation
- The role title and company if known
- One or two proof points you want to reference (specific results, not job titles)
- Any prior relationship with this person (previous conversation, mutual connection, prior application)
- The platform: LinkedIn message, email, or other
If you do not provide proof points, the skill will ask for them. A message built on generic claims will not perform.
The Strategic Decisions Behind Every Message
Before writing, make these decisions explicitly. Getting them wrong is why most outreach fails.
Decision 1: What is the reader's actual problem?
A recruiter who posted a Director of Demand Gen role is trying to find someone who can generate pipeline for a B2B SaaS company without a lot of hand-holding. That is the problem. Not "a demand gen leader with 10 years of experience." The message should open by making it immediately clear you solve that problem.
A hiring manager who owns a revenue target is trying to find someone who will not make their pipeline problem worse. They are not reading resumes for credentials. They are reading for signals that you have done this before at a similar scale and know what you are doing.
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 · 330 lines · 199 tokens per session scan A 58f81517648b
recruiter-outreach is a skill published in the GitHub repository modest-curator478/claude-skills (4 stars, last pushed yesterday), licensed MIT. It adds 199 tokens to every session and 2,523 once invoked, about $0.0010 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to recruiter-outreach, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
TEMPLATE
../../../agents/personas/TEMPLATE.md.
debug
Systematic debugging using error-detective and debugger agents instead of manual investigation. Triggers automatically on: error, bug, broken, failing, exception, stack trace, test failure. Orchestrates RCA-first approach with parallel agent investigation.
deep-context
Build deep codebase understanding using Capsule context, progressive-reader, and specialist agents instead of overwhelming main context. Triggers on: don't have context, understand codebase, learn about, need background. Implements progressive context building.
workflow
Systematic task orchestration for complex multi-step tasks. Triggers automatically when detecting: complex task, multi-step work, coordinate, orchestrate, break down. Guides through Understand → Strategy → Plan → Execute → Verify phases for comprehensive systematic approach.
task-router
Decision matrix for choosing optimal approach to any task. Helps Claude decide when to delegate to sub-agents vs. working directly. Use when starting a new task or unsure of best approach.
nextdns-cli
NextDNS CLI client best practices for installation, configuration, and management of DNS-over-HTTPS proxy. This skill should be used when installing NextDNS on routers, servers, or client devices, configuring DNS settings, managing the daemon, or troubleshooting DNS issues. Triggers on tasks involving NextDNS CLI…