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 wtznicy/my-websearch --skill my-websearch-maintainergit clone --depth 1 https://github.com/wtznicy/my-websearchWrote 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/wtznicy/my-websearch/my-websearch-maintainer)<a href="https://agentmods.dev/skills/wtznicy/my-websearch/my-websearch-maintainer"><img src="https://agentmods.dev/badge/skills/wtznicy/my-websearch/my-websearch-maintainer/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/wtznicy/my-websearch/my-websearch-maintainer"><img src="https://agentmods.dev/badge/skills/wtznicy/my-websearch/my-websearch-maintainer.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.00043 | $0.00692 |
| Opus 5.5 | $0.00017 | $0.00277 |
| Sonnet 5.5 | $0.00009 | $0.00138 |
| Haiku 4.5 | $0.00004 | $0.00069 |
Grade A, and why
my-websearch-maintainer 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 1mo 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
97% identical to open-websearch-maintainer — 6 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 — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Open WebSearch Maintainer
Use this skill when modifying the my-websearch codebase itself.
If this skill and the current repository behavior disagree, trust the repository code, tests, and intended change scope, then update the skill or docs before finishing.
First classify the change
- Engine change: new engine, engine parsing, engine pagination, anti-bot handling.
- Network change: proxy, TLS, request builder, Playwright interaction, browser fallback.
- Tool surface change: MCP tool registration, schema, engine normalization, config exposure.
- Validation-only change: tests, docs, or release hygiene when no code-path behavior changes are intended.
Use this classification as the execution entrypoint. Start by choosing one category, load only the checklist that matches it, and expand scope only when the changed code path actually crosses that boundary.
Scope discipline
- Keep fixes as local as the real failure surface allows.
- Do not turn a parsing or engine-specific issue into a shared networking refactor without evidence.
- Do not widen insecure or compatibility-relaxing behavior just to make one test pass.
- Do not change tool contracts or global behavior unless the change is intentional, verified, and documented.
Core rules
- Keep MCP tool contracts stable unless the change explicitly requires a breaking change.
- Route Axios-based networking through the shared HTTP request builder instead of ad hoc proxy handling.
- Treat proxy, TLS, and Playwright behavior as cross-cutting concerns. Verify them explicitly after changes.
- Update tests and README files when adding engines or changing behavior.
Do not
- Do not bypass the shared HTTP request builder for a one-off engine fix.
- Do not silently fork proxy behavior in a single engine unless the repository explicitly adopts that policy.
- Do not widen insecure TLS behavior beyond the narrow code path that requires it.
- Do not change tool contracts without checking tests, config handling, and README files.
- Do not touch shared networking code if the change is only about result parsing or docs.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 1mo ago First seen · 73 lines · 43 tokens per session scan A b3158dfb8aed
my-websearch-maintainer is a skill published in the GitHub repository wtznicy/my-websearch (2 stars, last pushed yesterday), licensed Apache-2.0. It adds 43 tokens to every session and 692 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 97% identical to open-websearch-maintainer, differing in 6 lines, and is treated as a copy.
Other skills, from other repositories
ddgs
Use when an agent needs to search the web, find images/news/videos/books, or extract content from a URL. Covers the ddgs Python library, CLI, and MCP server integration.
frontmcp-extensibility
Use when extending FrontMCP beyond the core SDK by integrating external npm packages, libraries, or third-party services into providers and tools. Covers VectoriaDB for in-memory semantic and vector search (ML-based embeddings or TF-IDF keyword engines, with persistence) and the tamper-evident, hash-chained skill…
solr-query
To build and debug Solr queries: eDisMax, block join, JSON facets, kNN, explain.
Fetch a Reddit post URL via old.reddit.com HTML scraping — the .json API is blocked for unauthenticated requests since May 2026. Returns structured data: post metadata + nested comments (with depth) + unique external links categorized (github/reddit/external). Persists into capstore tables (reddit.posts, .comments…
everything-http-server
A Windows setup guide for enabling Everything’s read-only HTTP search server. Everything is a desktop file-search tool; its HTTP server lets another local tool search files through a web request.
vector-hybrid-search
Retrieve knowledge from a vector-store collection via the vector-mcp MCP server's vectorsearch tool — semantic (ANN) search, lexical BM25 search, or a hybrid of the two fused with Reciprocal Rank Fusion. Use when the agent must answer a question from an indexed corpus, pull top-k relevant chunks for RAG context, or…