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 fiber-ai/fiber-ai-plugin --skill expand-from-email-listgit clone --depth 1 https://github.com/fiber-ai/fiber-ai-pluginWrote 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/fiber-ai/fiber-ai-plugin/expand-from-email-list)<a href="https://agentmods.dev/skills/fiber-ai/fiber-ai-plugin/expand-from-email-list"><img src="https://agentmods.dev/badge/skills/fiber-ai/fiber-ai-plugin/expand-from-email-list/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/fiber-ai/fiber-ai-plugin/expand-from-email-list"><img src="https://agentmods.dev/badge/skills/fiber-ai/fiber-ai-plugin/expand-from-email-list.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.00107 | $0.01696 |
| Opus 5 | $0.00053 | $0.00848 |
| Sonnet 5 | $0.00021 | $0.00339 |
| Haiku 4.5 | $0.00011 | $0.00170 |
Grade A, and why
expand-from-email-list 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 — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fiber AI: Expand From Email List
Start from raw emails (CRM dump, signups, support tickets) and resolve them into people - LinkedIn URL, name, title, company, location - then optionally layer on fresh profile data or extra contact fields.
When to use
- User pastes or attaches emails and asks "who are these people?"
- User wants to decorate a CRM export with LinkedIn URLs and titles
- User wants to identify anonymous customers who signed up with an email
- User says "reverse lookup", "email to LinkedIn", "unknown customers enrichment"
Do not use when
- User already has LinkedIn URLs and needs contact data - use
/fiber:enrich-linkedin-csv - User wants to find new people matching a role - use
/fiber:find-and-enrich-by-role - User wants a saved, exportable audience - use
/fiber:audienceor/fiber:build-recruiting-audience - User wants code - use
/fiber:sdk-tsor/fiber:sdk-py
Happy path
Route by list size, then layer optional follow-up enrichment.
- Loop
reverseEmailLookuprow by row with a small concurrency cap (3-5 parallel). Surface progress as matches arrive. The public API currently only exposes the single-row endpoint; no bulk variant is registered. - For each returned LinkedIn URL, pick one follow-up based on what the user actually needs:
- Canonical profile snapshot (cheap, fast):
KitchenSinkProfile- preserve the PascalCase on this one. - Freshest LinkedIn data (current role, tenure, recent posts-derived signals):
profileLiveEnrich. Charges credits.
- Canonical profile snapshot (cheap, fast):
- If the user also needs phones or alternative emails on the now-identified people, pipe them into
syncQuickContactReveal(for <=5) or hand off to/fiber:enrich-linkedin-csvor/fiber:build-recruiting-audiencefor larger lists. - Always call out unmatched emails explicitly - reverse email match rates vary significantly by vintage and data source. Do not silently drop misses.
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 · 90 lines · 107 tokens per session scan A 34df048f7b2d
expand-from-email-list is a skill published in the GitHub repository fiber-ai/fiber-ai-plugin (2 stars, last pushed 2mo ago), licensed MIT. It adds 107 tokens to every session and 1,696 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…