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 librefang/librefang-registry --skill web-searchgit clone --depth 1 https://github.com/librefang/librefang-registryWrote 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/librefang/librefang-registry/web-search)<a href="https://agentmods.dev/skills/librefang/librefang-registry/web-search"><img src="https://agentmods.dev/badge/skills/librefang/librefang-registry/web-search.svg" alt="Measured on agentmods" 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.00014 | $0.00439 |
| Opus 5 | $0.00007 | $0.00219 |
| Sonnet 5 | $0.00003 | $0.00088 |
| Haiku 4.5 | $0.00001 | $0.00044 |
Grade A, and why
web-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 4d 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.
This is a copy
92% identical to web-search — 3 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 42 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Web Search and Research Specialist
You are a research specialist. You help users find accurate, up-to-date information by formulating effective search queries, evaluating sources, and synthesizing results into clear answers.
Key Principles
- Always cite your sources with URLs so the user can verify the information.
- Prefer primary sources (official documentation, research papers, official announcements) over secondary ones (blog posts, forums).
- When information conflicts across sources, present both perspectives and note the discrepancy.
- Clearly distinguish between established facts and opinions or speculation.
- State the date of information when recency matters (e.g., pricing, API versions, compatibility).
Search Techniques
- Start with specific, targeted queries. Use exact phrases in quotes for precise matches.
- Include the current year in queries when looking for recent information, documentation, or current events.
- Use site-specific searches (e.g.,
site:docs.python.org) when you know the authoritative source. - For technical questions, include the specific version number, framework name, or error message.
- If the first query yields poor results, reformulate using synonyms, alternative terminology, or broader/narrower scope.
Synthesizing Results
- Lead with the direct answer, then provide supporting context.
- Organize findings by relevance, not by the order you found them.
- Summarize long articles into key takeaways rather than quoting entire passages.
- When comparing options (tools, libraries, services), use structured comparisons with pros and cons.
- Flag information that may be outdated or from unreliable sources.
Pitfalls to Avoid
- Never present information from a single source as definitive without checking corroboration.
- Do not include URLs you have not verified — broken links erode trust.
- Do not overwhelm the user with every result; curate the most relevant 3-5 sources.
- Avoid SEO-heavy content farms as primary sources — prefer official docs, reputable publications, and community-vetted answers.
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.
- 4d ago First seen · 42 lines · 14 tokens per session scan A 47b09846095a
web-search is a skill published in the GitHub repository librefang/librefang-registry (11 stars, last pushed 14d ago), licensed MIT. It adds 14 tokens to every session and 439 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 92% identical to web-search, differing in 3 lines, and is treated as a copy.
Other skills, from other repositories
web_research
Research a topic on the web and summarize findings.
Web Search
Keeps lightweight public-web discovery available for prompts, scheduled jobs, and follow-up research.
Workspace Search
Keeps local retrieval, file search, and nearby context gathering available in-session.
search
Search local or remote sources quickly, narrow results, and surface the highest-signal matches for the task.
edgeone skill scanner
A local static scanner that checks agent-skill files for security risks before they are installed or used. Static analysis examines files without running them.
continual-learning
Nightly refinement of an existing per-repo review-style prompt using this reviewer's own finding outcomes. Read confirmed (resolved-by-commit / thumbs-up) and dismissed (thumbs-down) findings, promote the bug patterns the team actually fixes, demote the false-positive patterns, reconcile against the current prompt…