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 nimadorostkar/Claude-Skills-collection --skill lead-researchgit clone --depth 1 https://github.com/nimadorostkar/Claude-Skills-collectionWrote 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/nimadorostkar/claude-skills-collection/lead-research)<a href="https://agentmods.dev/skills/nimadorostkar/claude-skills-collection/lead-research"><img src="https://agentmods.dev/badge/skills/nimadorostkar/claude-skills-collection/lead-research/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/nimadorostkar/claude-skills-collection/lead-research"><img src="https://agentmods.dev/badge/skills/nimadorostkar/claude-skills-collection/lead-research.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.00038 | $0.01158 |
| Opus 5 | $0.00019 | $0.00579 |
| Sonnet 5 | $0.00008 | $0.00232 |
| Haiku 4.5 | $0.00004 | $0.00116 |
Grade A, and why
lead-research 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 — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Lead Research
Purpose
Research an account well enough that the outreach is obviously not a template. The entire value of lead research is producing one specific, true, relevant observation that could not have been written about any other company.
When to Use
- Researching an account before outreach.
- Qualifying inbound leads.
- Building a target list.
- Preparing for a sales call.
Capabilities
- Qualification against a defined profile.
- Trigger-event identification.
- Finding the right contact and the actual decision maker.
- Producing a brief that makes outreach specific.
Inputs
- The ideal customer profile, defined in observable terms.
- The account.
- What you are actually selling, and to what problem.
Outputs
- A qualification verdict with the reasoning.
- The trigger, if there is one.
- One specific observation that makes the outreach non-generic.
Workflow
- Qualify before researching — Does this account match the profile at all? Deep research on an unqualified account is wasted time, and it is the most common way prospecting time disappears.
- Find the trigger — What changed recently? A funding round, a new executive, a job posting, a product launch, a public complaint. Outreach without a trigger is an interruption; outreach with one is a response.
- Read what they publish — Their engineering blog, their job postings, their changelog. Job postings in particular are extraordinarily informative: they say exactly what a company is building and what it lacks.
- Find the person with the problem — Not the most senior person. The person who owns the pain is the one who will reply.
- Find one specific, true observation — Something that could not be written about any other company. This is the entire output; everything else is preparation for it.
- Stop when you have it — More research does not improve outreach past this point.
Best Practices
- Job postings are the most under-used signal in prospecting. A company hiring three platform engineers and a site reliability engineer is a company with a reliability problem, and they have just told you so in public.
- One specific observation beats five generic ones. "I saw you're hiring three platform engineers" is worth more than any amount of "I noticed your impressive growth".
- The trigger is what makes outreach timely. Without one, you are asking someone to change their priorities for a stranger.
- Do not personalize with something trivially scraped. "I see you're based in Austin" is not personalization; it is proof of automation.
- Qualify ruthlessly. Time spent researching an account that will never buy is the most expensive thing in prospecting.
- If you cannot find one specific, true, relevant observation, the account is not ready. Move on.
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 · 109 lines · 38 tokens per session scan A 4f9a27f2bb28
lead-research is a skill published in the GitHub repository nimadorostkar/Claude-Skills-collection (26 stars, last pushed 24d ago), licensed MIT. It adds 38 tokens to every session and 1,158 once invoked, about $0.0002 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
offensive-c2-frameworks
Command and Control framework deployment, configuration, and operational tradecraft for red team engagements. Covers Cobalt Strike (malleable C2 profiles, Beacon types HTTP/HTTPS/DNS/SMB, Beacon Object Files for in-memory execution, sleep and jitter tuning, named pipe pivoting), Sliver (implant generation across…
offensive-crypto-attacks
Systematic methodology for identifying and exploiting cryptographic implementation weaknesses in real-world applications. Covers padding oracle attacks against CBC-mode ciphers with PKCS7 padding (Vaudenay's original attack through modern padbuster automation), ECB mode exploitation including block cut-and-paste and…
offensive-parameter-pollution
HTTP parameter pollution (HPP) checklist: duplicate parameter injection, backend vs frontend parsing differences, WAF bypass via HPP, server-side vs client-side HPP, and practical exploitation patterns. Use when testing web applications for parameter handling flaws.
offensive-wifi
Wireless / 802.11 attack methodology for red team engagements and wireless security assessments. Covers monitor-mode setup, WPA/WPA2-PSK handshake capture and PMKID attacks, WPA3 SAE downgrade and Dragonblood, WPA-Enterprise (EAP) attacks (MSCHAPv2 cracking, EAP-TLS cert theft, evil-twin RADIUS), Karma / Known Beacons…
offensive-z-wave
Z-Wave attack methodology — sniffing with Z-Force / EZ-Wave / RTL-SDR + ZniffMobile, S0 (legacy) network-key derivation flaw and key reuse, S2 (modern) ECDH commissioning analysis, replay/injection on unauthenticated nodes, default-key brute-force on test deployments, and home-automation hub pivots. Use when targeting…
seo
Optimize for search engine visibility and ranking. Use when asked to "improve SEO", "optimize for search", "fix meta tags", "add structured data", "sitemap optimization", or "search engine optimization".