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 theYahia/WWmcp --skill competitor-scangit clone --depth 1 https://github.com/theYahia/WWmcpWrote 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/theyahia/wwmcp/competitor-scan)<a href="https://agentmods.dev/skills/theyahia/wwmcp/competitor-scan"><img src="https://agentmods.dev/badge/skills/theyahia/wwmcp/competitor-scan/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/theyahia/wwmcp/competitor-scan"><img src="https://agentmods.dev/badge/skills/theyahia/wwmcp/competitor-scan.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.00023 | $0.00541 |
| Opus 5 | $0.00012 | $0.00270 |
| Sonnet 5 | $0.00005 | $0.00108 |
| Haiku 4.5 | $0.00002 | $0.00054 |
Grade A, and why
competitor-scan 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.
What it actually says
/competitor-scan — Category density and ratings
Algorithm
- Resolve the location: call
geocodeon the address the user gave, take lat/lon. - Resolve the category. If the user gave a 2GIS rubric_id, use it directly with
search_by_rubric. If they gave a name ("barbershop", "coffee"), usesearch_placeswith that query and type = org instead — there is no rubric lookup tool in this server. - Call
search_by_rubric(orsearch_places) with point = "lon,lat" and radius (default 1500). Note the total count — that is the density number. - For the top 5 results call
get_reviewswith each place_id. Record rating and review count. - For the two highest-rated call
get_placeto pull schedule and contacts. - Summarize: how many competitors, rating spread, who dominates, where the gap is (low ratings, few reviews, short opening hours).
Response format
## Barbershops within 1.5 km of Arbat 12
**Density**: 23 in radius
**Rating spread**: 3.4 — 4.9 (median 4.3)
| # | Name | Rating | Reviews | Hours |
|---|------|--------|---------|-------|
| 1 | ... | 4.9 | 480 | 10:00–22:00 |
**Gap**: 9 of 23 have under 20 reviews — thin social proof in this radius.
Notes
- Report only what the tools returned. Do not estimate revenue or traffic — 2GIS has no such fields.
get_reviewsaccepts an optional limit; keep it small (10) since only the aggregate matters.- A large total with a small returned page is normal: increase page_size on
search_placesor paginate before claiming a number is final.
Examples
/competitor-scan barbershop "Arbat 12" 1500
/competitor-scan "coffee shop" 55.7558,37.6173
/competitor-scan pharmacy "Kazan, Bauman 5" 800
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 · 52 lines · 23 tokens per session scan A 68fe6d216acb
competitor-scan is a skill published in the GitHub repository theYahia/WWmcp (29 stars, last pushed 2d ago), licensed MIT. It adds 23 tokens to every session and 541 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-09-06.
Other skills, from other repositories
javascript-typescript
Professional JavaScript and TypeScript development skill covering modern ES6+, TypeScript, Node.js, Express, React, testing frameworks, and best practices. Use this skill when developing JavaScript/TypeScript applications, building React/Node.js projects, implementing RESTful APIs, or need guidance on modern JS/TS…
okx-cex-earn
A tool for managing several earning products on OKX, including savings, lending, staking, DeFi, Dual Investment, and AutoEarn. These products can use deposited cryptocurrency to generate returns, with terms that vary by product.
okx-cex-smartmoney
An OKX tool for studying activity from high-performing traders, sometimes called “smart money.” It shows trader rankings, positions, trades, past results, and combined signals.
adding-a-command
Creates a new CLI command following the Commander.js pattern in src/commands/. Handles command registration in src/cli.ts, telemetry tracking via tracked() wrapper, and option parsing. Use when user says add command, new CLI command, create subcommand, or adds files to src/commands/. Do NOT use for modifying existing…
typescript-patterns
TypeScript types: generics, discriminated unions, Zod, satisfies, branded types. Triggers: TypeScript, TS, generics, Zod, satisfies, strict mode.
aba-precision-protocol
FOUNDATIONAL BEHAVIORAL PROTOCOL — ABA-based precision execution rules. Every prompt processed must follow these rules. Mistakes caught late create intermittent reinforcement of wrong patterns. Stop-fix-verify before proceeding.