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 Zevenue/headless-gtm --skill 06-resolution-email-persongit clone --depth 1 https://github.com/Zevenue/headless-gtmWrote 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/zevenue/headless-gtm/06-resolution-email-person)<a href="https://agentmods.dev/skills/zevenue/headless-gtm/06-resolution-email-person"><img src="https://agentmods.dev/badge/skills/zevenue/headless-gtm/06-resolution-email-person/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/zevenue/headless-gtm/06-resolution-email-person"><img src="https://agentmods.dev/badge/skills/zevenue/headless-gtm/06-resolution-email-person.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, 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 27 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.
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.00147 | $0.03021 |
| Opus 5 | $0.00073 | $0.01510 |
| Sonnet 5 | $0.00029 | $0.00604 |
| Haiku 4.5 | $0.00015 | $0.00302 |
Grade A, and why
06-resolution-email-person scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
Each provider reads its API key from an **environment variable** - `AIARK_API_KEY`, `PROSPEO_API_KEY`, `BLITZ_API_KEY`, `FINDYMAIL_API_KEY`, `ZEROBOUNCE_API_KEY` - never hardcode a key. This skill calls the providers wit How it starts
The opening of the file, as written. The whole thing — 135 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Resolution - Email + Person
Turn {domain (required), optional person_name, optional job_title} into a verified, send-safe email.
The one principle that governs every decision here: bounce rate, not find rate, is the signal that matters. A found-but-undeliverable email is worse than no email - it burns sender reputation. So this skill optimizes for deliverable contacts at minimum credit cost, and it never spends enrichment credit without the user's explicit go-ahead.
domain is the one mandatory input across every tool. Everything else can be asked for, inherited from upstream, or derived.
Provider + auth setup
Each provider reads its API key from an environment variable - AIARK_API_KEY, PROSPEO_API_KEY, BLITZ_API_KEY, FINDYMAIL_API_KEY, ZEROBOUNCE_API_KEY - never hardcode a key. This skill calls the providers with curl, and a .env file is not visible to curl - load it into the shell in the same command as the call, otherwise an empty auth header comes back as a provider auth error rather than a missing-key one:
set -a; [ -f .env ] && . ./.env; set +a
An exported variable or a secrets manager takes precedence and needs no prelude. The skill runs with as few as one key set: at startup, detect which keys are present, use only those rungs, and skip the rest (log which rungs were skipped and why). Read references/providers.md for endpoints, request shapes, billing rules, and rate limits before making any call.
- AI Ark - rung 0, conditional: runs only if
AIARK_API_KEYis set. Two modes. (a) Passthrough: a row that already carries an AI Ark-verified email (source flagai_ark/pre_verified, or the caller says the list is an AI Ark export) is accepted as-is - don't re-find what's already verified. (b) Finder:POST /people/export/singleturns a LinkedIn profile URL or AI Ark person id (not name+domain) into a BounceBan-verified email - 1 credit per valid email, 0 on a miss. Strong on SMB operators where Prospeo is weak. ThePOST /peoplesearch bills separately (~0.5 credit per returned profile), so keep searches tightly filtered and prefer/people/export/single. - Prospeo - title-first finder, strong on mid-market + enterprise. Charged only when a request returns results (misses are free).
- Blitz - domain-first finder, strong on SMB. Free on Blitz's Unlimited plan (verify your own plan before treating it as free). Two steps:
domain-to-linkedin→employee-finder(nativejob_level/job_functionfilters); returns the person but not the email. - Findymail - email finder by name+domain (
POST /api/search/name- NOT/api/find, which 405s; seereferences/providers.md). - ZeroBounce - independent email validation (
GET /v2/validate). If its key isn't set, fall back to the finding provider's bundled verdict. Explicitcatch-allstatus (no false "ok" on catch-all domains), and unknown results consume no credit.
What ships with it
3 files 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 · 135 lines · 147 tokens per session scan A a3d4ab4927c3
06-resolution-email-person is a skill published in the GitHub repository Zevenue/headless-gtm (27 stars, last pushed 1mo ago), licensed MIT. It adds 147 tokens to every session and 3,021 once invoked, about $0.0007 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
gtm-machine
Validate startup ideas with evidence and test them with real outbound — the full loop from raw idea to booked calls. Use this skill whenever an idea-stage founder wants to validate a startup or product idea, assess AI-platform kill-risk, check if a market is worth entering, build an ICP or personas, source leads from…
deepline-ads-audiences
Use this skill when building, enriching, auditing, or uploading B2B paid ads audiences to Google Customer Match, Meta/Facebook Custom Audiences, or LinkedIn Matched Audiences. Triggers on phrases like '/deepline-ads-audience', '/deepline-ads-audiences', 'upload this audience', 'create custom audiences', 'personal…
deepline-gtm
GTM prospecting, enrichment, outreach, and Deepline Play work/audits. Providers…
deepline-pre-research
Use when the user wants a last30days-style pre-research pass in Deepline: discover the critical public, private, CRM, workflow, social, and web data sources for a research/enrichment job; compare provider coverage; estimate Deepline credit cost; recommend the source plan before building or running the workflow; or…
deepline-analytics
Use this skill when answering business analytics, RevOps, GTM metric, pipeline, revenue, funnel, customer, or warehouse questions with Deepline. Triggers on phrases like 'query Snowflake', 'analyze pipeline', 'total ACV', 'break down by quarter', 'use the semantic layer', 'run a semantic query', or any use of…
niche-signal-discovery
Discover niche first-party signals that differentiate Closed Won vs Closed Lost accounts for ICP analysis. Use when the user provides won/lost customer domain lists and wants differential signals (website content, job listings, tech stack, maturity markers) to build account scoring models and prospecting criteria.…