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 find-and-enrich-by-rolegit 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/find-and-enrich-by-role)<a href="https://agentmods.dev/skills/fiber-ai/fiber-ai-plugin/find-and-enrich-by-role"><img src="https://agentmods.dev/badge/skills/fiber-ai/fiber-ai-plugin/find-and-enrich-by-role/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/find-and-enrich-by-role"><img src="https://agentmods.dev/badge/skills/fiber-ai/fiber-ai-plugin/find-and-enrich-by-role.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.00097 | $0.01966 |
| Opus 5 | $0.00048 | $0.00983 |
| Sonnet 5 | $0.00019 | $0.00393 |
| Haiku 4.5 | $0.00010 | $0.00197 |
Grade A, and why
find-and-enrich-by-role 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 — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fiber AI: Find and Enrich By Role
Discover prospects by role and company, then reveal contact details for the shortlist the user actually wants to reach. The default sales-prospecting combo skill.
When to use
- User asks for people by role + company criteria ("VPs of Eng at fintech startups")
- User wants a short, chat-time list (under 50 rows) with emails/phones attached
- User says "prospect by role", "sales target research", "find me N s in "
- User wants a quick pass before deciding whether to build a full audience
Do not use when
- User wants a saved, exportable list of 100+ prospects - use
/fiber:audienceor/fiber:build-recruiting-audience - User already has LinkedIn URLs - use
/fiber:enrich-linkedin-csv - User only wants to search, not reveal contacts - use
/fiber:search - User wants code - use
/fiber:sdk-tsor/fiber:sdk-py
Happy path
One search entry, one shared enrichment tail.
- Map the user's brief into
peopleSearch'ssearchParams. Fiber's search uses typed seniority levels (vp,director,c-level) and canonicalized company slugs — no regex or case-normalization needed. If the user only gave freeform prose (e.g. "VPs of Engineering at Series B fintechs in NYC") and you cannot extract clean filters, usetextToProfileSearchto translate intent into structured filters automatically, or hand the whole prompt to the Core MCPsearch_endpointsmeta-tool so it picks the correct route; do not invent fields. Runget_endpoint_details_full("peopleSearch")on the Core MCP for the currentsearchParamsschema. - Call
peopleSearchwith the mapped filters. Always echo the filters you used back to the user in one line so they can correct before paginating ("using: title=VP Engineering, industry=Fintech, funding=Series B, location=NYC - edit or proceed?"). - Before paginating, call
peopleSearchCountwith the same filters and surface the total ("4,120 people match - show page 1 of 25, or narrow first?"). Never silently page past page 1. KeeppageSize <= 50. - User picks a shortlist (typically <= 25). For each row, call
syncQuickContactReveal. For shortlists of 26-500, usestartBatchContactDetails+pollBatchContactDetailsinstead - cheaper per row and async. - If the shortlist grows past ~50 or the user asks to export, stop and hand off to
/fiber:build-recruiting-audienceor/fiber:audience. Those flows are cheaper and more robust at that scale.
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 · 107 lines · 97 tokens per session scan A 726fb4d0ee2a
find-and-enrich-by-role is a skill published in the GitHub repository fiber-ai/fiber-ai-plugin (2 stars, last pushed 2mo ago), licensed MIT. It adds 97 tokens to every session and 1,966 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…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
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…