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 find-nearbygit 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/find-nearby)<a href="https://agentmods.dev/skills/theyahia/wwmcp/find-nearby"><img src="https://agentmods.dev/badge/skills/theyahia/wwmcp/find-nearby/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/find-nearby"><img src="https://agentmods.dev/badge/skills/theyahia/wwmcp/find-nearby.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.00026 | $0.00479 |
| Opus 5 | $0.00013 | $0.00239 |
| Sonnet 5 | $0.00005 | $0.00096 |
| Haiku 4.5 | $0.00003 | $0.00048 |
Grade A, and why
find-nearby 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 6d 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
/find-nearby — Places around a point
Algorithm
- If the user gave an address instead of coordinates, call
geocodewith it and take lat/lon from the first result. If they gave coordinates, skip this step. - Call
search_placeswith query = what the user is looking for, point = "lon,lat" (2GIS expects longitude first), radius in meters (default 1000), page_size = 10. - If nothing is found, widen radius to 5000 and retry once before reporting an empty result.
- For the top 3 results call
get_reviewswith their place_id to pull rating and recent review count. Skip this if the user asked for a plain list. - If a result looks ambiguous, call
get_placewith its place_id for the full card (schedule, phones, website).
Response format
## Cafes within 1 km of Tverskaya 7
| # | Name | Address | Rating | Distance |
|---|------|---------|--------|----------|
| 1 | Coffee Bean | Tverskaya 9 | 4.6 (312) | 180 m |
| 2 | ... | | | |
Total found: 47 — showing top 10.
Notes
search_placestakes point as a single "lon,lat" string, not two numbers.- The type filter accepts building, street, branch, org, adm_div — use org for businesses.
get_reviewstakes a place_id from a search result, not a name.- 2GIS covers Russia and CIS. Outside that footprint results will be empty — say so instead of retrying.
Examples
/find-nearby pharmacy 55.7558,37.6173
/find-nearby coffee "Nevsky prospekt 28" 500
/find-nearby ATM Sberbank Kazan center
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.
- 6d ago First seen · 49 lines · 26 tokens per session scan A 578dd287232f
find-nearby is a skill published in the GitHub repository theYahia/WWmcp (29 stars, last pushed 5d ago), licensed MIT. It adds 26 tokens to every session and 479 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.