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 feniix/pi-extensions --skill people-researchgit clone --depth 1 https://github.com/feniix/pi-extensionsWrote 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/feniix/pi-extensions/people-research)<a href="https://agentmods.dev/skills/feniix/pi-extensions/people-research"><img src="https://agentmods.dev/badge/skills/feniix/pi-extensions/people-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/feniix/pi-extensions/people-research"><img src="https://agentmods.dev/badge/skills/feniix/pi-extensions/people-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.00021 | $0.00634 |
| Opus 5 | $0.00010 | $0.00317 |
| Sonnet 5 | $0.00004 | $0.00127 |
| Haiku 4.5 | $0.00002 | $0.00063 |
Grade A, and why
people-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 — 48 lines — stays where its author put it; the contents beside it link to each section on GitHub.
People Research (Exa)
Use this skill for finding experts, candidates, speakers, authors, investors, founders, maintainers, or other public professional profiles.
Tool Selection
| Intent | Primary Tool | Notes |
|---|---|---|
| Professional profile discovery | web_search_advanced_exa with category: "people" |
Use when available; put role, domain, company, or location in query. |
| Broad discovery when advanced search is unavailable | web_search_exa |
Use precise role/company/topic terms and public-profile keywords. |
| Compare multiple people or build a shortlist | web_research_exa |
Use when enabled; include selection criteria in systemPrompt. |
| Direct factual question about one person | web_answer_exa |
Good for short cited checks. |
| Read selected profile pages or bios | web_fetch_exa |
Fetch only high-signal URLs. |
| Find similar profiles from a strong seed page | web_find_similar_exa |
Use when one public profile is an ideal example. |
If web_search_advanced_exa is unavailable, fall back to web_search_exa. If web_research_exa is unavailable, provide a sourced shortlist without deep synthesis.
Filter Restrictions
When using web_search_advanced_exa with category: "people", avoid:
excludeDomainsstartPublishedDate/endPublishedDate
For includeDomains, only LinkedIn domains are accepted by the extension for category: "people", such as linkedin.com or www.linkedin.com.
Recommended Settings
- People discovery
{ "query": "distributed systems database engineer San Francisco", "category": "people", "numResults": 10 }
- LinkedIn-scoped people discovery
{ "query": "AI infrastructure startup founder", "category": "people", "includeDomains": ["linkedin.com"], "numResults": 10 }
- Deep shortlist comparison
{ "query": "Find public experts in database internals and distributed systems who write about production engineering trade-offs.", "systemPrompt": "Prefer public bios, personal sites, talks, publications, and reputable profiles. Flag common-name ambiguity and sparse evidence.", "outputSchema": { "type": "object", "properties": { "experts": { "type": "array", "items": { "type": "object" } }, "caveats": { "type": "array", "items": { "type": "string" } } } } }
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 · 48 lines · 21 tokens per session scan A c92c840fbef1
people-research is a skill published in the GitHub repository feniix/pi-extensions (23 stars, last pushed 8d ago), licensed MIT. It adds 21 tokens to every session and 634 once invoked, about $0.0001 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
qamap-pr-qa
Local zero-LLM PR QA workflow. Use when an agent is preparing, updating, finalizing, or reviewing a pull request, asks what the PR should test, or needs commit-backed change intent, affected behavior, QA scenarios, evidence, validation commands, optional automation drafts, and manifest repair guidance.
ts-debug
TypeScript/Node debugging expert. Use when the user needs to debug, profile, or trace TypeScript or Node.js code — e.g. "how do I debug this", "find the memory leak", "why is this slow", "add a breakpoint", "profile this function", "why won't the process exit".
typescript-conventions
Use when writing, reviewing, or refactoring TypeScript or JavaScript code — naming conventions, type annotations, private fields, null vs. undefined, async/await pitfalls, and module structure.
migrate-to-shoehorn
Migrate test files from as type assertions to @total-typescript/shoehorn. Use when user mentions shoehorn, wants to replace as in tests, or needs partial test data.
setup-ts-deep-modules
Wire dependency-cruiser into a TypeScript repo so each package is a deep module — implementation hidden in subfolders, reachable only through its entry-point files. User-invoked.
migrate-to-shoehorn
Migrate test files from as type assertions to @total-typescript/shoehorn. Use when user mentions shoehorn, wants to replace as in tests, or needs partial test data.