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 personal-site-searchgit 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/personal-site-search)<a href="https://agentmods.dev/skills/feniix/pi-extensions/personal-site-search"><img src="https://agentmods.dev/badge/skills/feniix/pi-extensions/personal-site-search/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/personal-site-search"><img src="https://agentmods.dev/badge/skills/feniix/pi-extensions/personal-site-search.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.00020 | $0.00742 |
| Opus 5 | $0.00010 | $0.00371 |
| Sonnet 5 | $0.00004 | $0.00148 |
| Haiku 4.5 | $0.00002 | $0.00074 |
Grade A, and why
personal-site-search 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 11d 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 — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Personal Site Search (Exa)
Use this skill to find practitioner blogs, independent analysis, personal websites, technical essays, field notes, and non-corporate perspectives.
Tool Selection
| Intent | Primary Tool | Notes |
|---|---|---|
| Find practitioner blogs by topic | web_search_exa |
Start here when you do not already know a source site. |
| Filter to personal sites only | web_search_advanced_exa with category: "personal site" |
Use when available; add date or domain filters when useful. |
| Find more like this / recommend similar sites | web_find_similar_exa |
Use when you already have one strong post or blog URL. |
| Distill viewpoints across multiple posts | web_research_exa |
Use when enabled and synthesis is worth the cost. |
| Direct one-off answer from discovered sources | web_answer_exa |
Use for concise cited answers after the topic is clear. |
| Pull full article bodies | web_fetch_exa |
Fetch selected URLs when snippets are not enough. |
If web_search_advanced_exa is unavailable, use web_search_exa with terms like blog, personal site, independent write-up, or practitioner perspective.
When to Use Find-Similar vs Search
- Use
web_find_similar_exafor find more like this workflows when you already have a canonical URL that matches the taste, style, or niche you want. - Use
web_search_exafor keyword-based discovery when you are starting from a topic, technology, or opinion and do not yet have a seed URL. - Use
web_search_advanced_exainstead ofweb_find_similar_exawhen you need explicit controls likecategory: "personal site", domain constraints, or date filtering.
Recommended Settings
- Topic discovery
{ "query": "Rust async architecture practitioner blog", "numResults": 10 }
- Personal-site category search
{ "query": "Rust async architecture", "category": "personal site", "excludeDomains": ["medium.com", "substack.com"], "numResults": 15 }
- Similar-source expansion
{ "url": "https://example.dev/posts/rust-async-architecture", "excludeSourceDomain": true, "numResults": 8 }
- Synthesis
{ "query": "Compare recommendations from practitioner blogs about Rust async architecture trade-offs.", "systemPrompt": "Prioritize dated posts and independent authors. Distinguish opinion from verified facts and call out disagreement.", "outputSchema": { "type": "text" } }
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.
- 11d ago First seen · 53 lines · 20 tokens per session scan A d48df6a74743
personal-site-search is a skill published in the GitHub repository feniix/pi-extensions (23 stars, last pushed 7d ago), licensed MIT. It adds 20 tokens to every session and 742 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.