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 agentmods add skills/sydasif/web-search-mcp/debugnpx skills add sydasif/web-search-mcp --skill debuggit clone --depth 1 https://github.com/sydasif/web-search-mcpWrote 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/sydasif/web-search-mcp/debug)<a href="https://agentmods.dev/skills/sydasif/web-search-mcp/debug"><img src="https://agentmods.dev/badge/skills/sydasif/web-search-mcp/debug.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 | $0.00055 | $0.02209 |
| Opus 5 | $0.00028 | $0.01104 |
| Sonnet 5 | $0.00011 | $0.00442 |
| Haiku 4.5 | $0.00006 | $0.00221 |
Grade A, and why
debug 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 today.
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 — 165 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Debug Code
Operating Principle
Treat errors as symptoms until evidence shows the cause. Work from the most concrete signal available: exact command, full output, local code, recent changes, tests, current docs/source for external dependencies, then the smallest fix that explains all observed behavior.
Do not jump straight from an error string to an edit. First reproduce, isolate, explain, then change.
Tool Priority
Use the best available tool for the evidence needed. Do not block debugging just because a preferred tool is missing.
- Local CLI first:
rg,rg --files,git status,git diff, focused tests, logs, dependency manifests, lockfiles, and local dependency source. - Context7: use for current, version-aware library/framework documentation and code examples when dependency behavior matters.
- GitHub CLI (
gh): use for GitHub-native evidence such as issues, PRs, checks, releases, repo metadata, source files, and API calls from the terminal. - Web Search MCP: 10 tools total — the most relevant ones for debugging are organized into two tiers below. Use the cheapest tool that answers the question.
Web Search MCP — Tool Reference (10 tools)
Tier 1 — Direct Search & Retrieval (start here)
| Tool | What It Does | When To Use |
|---|---|---|
search_web |
DuckDuckGo or Exa web/news search (via provider param) |
Broad search for error messages, known bugs, solutions, release notes |
search_web (domain) |
DuckDuckGo (site:) or Exa (include_domains) scoped to domain | Targeted search on official docs (e.g. docs.python.org, react.dev) |
fetch_page |
Clean HTML-to-markdown extraction from any URL | Reading docs, changelogs, error pages, issue threads cleanly; Exa fallback handles JS/bot-blocked pages |
search_wikipedia |
Wikipedia article search via MediaWiki API | Fact-checking, background reference, terminology lookups |
search_arxiv |
Academic paper search via arXiv API | Finding research papers, literature reviews, citations |
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.
- today Changed · +1 lines d622fab8be84
- 4d ago First seen · 164 lines · 55 tokens per session scan A 22974dbb108e
debug is a skill published in the GitHub repository sydasif/web-search-mcp (24 stars, last pushed 3d ago), licensed MIT. It adds 55 tokens to every session and 2,209 once invoked, about $0.0003 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
opencli-usage
Use when running OpenCLI commands to interact with websites (Bilibili, Twitter, Reddit, Xiaohongshu, etc.), desktop apps (Cursor, Notion), or public APIs (HackerNews, arXiv). Covers installation, command reference, and output formats for 100+ adapters.
qiaomu-opencli-usage
Use when running OpenCLI commands to interact with websites (Bilibili, Twitter, Reddit, Xiaohongshu, etc.), desktop apps (Cursor, Notion), or public APIs (HackerNews, arXiv). Covers installation, command reference, and output formats for 79+ adapters.
mk:wiki-research
Fetch external sources (web / arXiv / GitHub) and turn them into scanner-gated wiki CANDIDATES — never canonical pages. Every fetched byte is DATA; url-guarded, size-capped, redirect-re-validated, injection-scanned, and secret-scrubbed before a candidate is even created. Requires network. NOT for capturing local…
opencli
OpenCLI — Make any website or Electron App your CLI. Zero risk, AI-powered, reuse Chrome login.
issue-triage
Issue triage: audit open issues, categorize, detect duplicates, cross-ref PRs, risk assessment, post comments. Args: "all" for deep analysis of all, issue numbers to focus (e.g. "42 57"), "en"/"fr" for language, no arg = audit only in French.
issue
Use when starting a chain from a GitHub issue — turning an issue URL or number into a triaged, planned, dispatched, and reviewed pull request. Classifies the thread (bug → root-cause discipline, feature → plan chain, question → drafted reply), synthesizes a spec from the issue's own acceptance criteria, then runs the…