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-contactgit 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-contact)<a href="https://agentmods.dev/skills/theyahia/wwmcp/find-contact"><img src="https://agentmods.dev/badge/skills/theyahia/wwmcp/find-contact/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-contact"><img src="https://agentmods.dev/badge/skills/theyahia/wwmcp/find-contact.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.00021 | $0.00662 |
| Opus 5.5 | $0.00008 | $0.00265 |
| Sonnet 5.5 | $0.00004 | $0.00132 |
| Haiku 4.5 | $0.00002 | $0.00066 |
Grade A, and why
find-contact 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.
How it starts
The opening of the file, as written. The whole thing — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/find-contact — Найти или завести контакт
Алгоритм
search(query — минимум 3 символа, limit до 250) — сквозной поиск по сделкам, контактам и компаниям. Первый шаг всегда он: он единственный ищет сразу по трём сущностям.- Уточни точечно, если сквозной поиск дал шум:
list_contacts(query, page, limit, with) — по имени, телефону, email;list_companies(query, page, limit, with) — по названию компании.
- Открой карточку:
get_contact(contact_id, with) — включая кастомные поля с телефоном и почтой. - Проверка дубля обязательна перед созданием. Один и тот же телефон в двух карточках ломает всю последующую аналитику. Нашёл совпадение — покажи его и спроси, создавать ли новое.
- Создание контакта:
create_contact(name или first_name + last_name, responsible_user_id, custom_fields_values — сюда кладутся телефон и email). - Создание компании:
create_company(name, responsible_user_id, custom_fields_values — адрес, сайт). - Зафиксируй, откуда контакт:
add_note(entity_id, entity_type: contacts, note_type, text). - Что по нему уже происходило —
list_events(entity: contacts, entity_id, page, limit) и связанные сделки черезlist_leads(query).
Важно
- Телефон и email в amoCRM живут не в обычных полях, а в custom_fields_values: без правильных ID полей значения не запишутся. Справочники аккаунта смотри в
get_account. searchтребует минимум 3 символа — на более коротком запросе не пытайся, попроси уточнить.- Объединения дублей среди инструментов нет: если дубль уже создан, сообщи пользователю, что чистить надо в интерфейсе amoCRM.
Формат ответа
## Поиск: «+79001234567»
### Найдено
| Тип | Название | ID | Ответственный |
|-----|----------|----|---------------|
| Контакт | Иванов Иван | 55120 | Петров |
| Сделка | Поставка Q3 | 88123 | Петров |
Дубль найден — новый контакт не создаю. Нужен новый? Скажите явно.
### Карточка 55120
Телефон: +79001234567 · Email: [email protected]
Компания: ООО Ромашка · Сделок: 3
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 · 53 lines · 21 tokens per session scan A ee6fb4ab47d5
find-contact is a skill published in the GitHub repository theYahia/WWmcp (36 stars, last pushed 1mo ago), licensed MIT. It adds 21 tokens to every session and 662 once invoked, about $0.0001 per session on Opus 5.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
gitlab-discovery
Find a GitLab project or namespace and establish the exact target for follow-up repository, merge request, work-item or CI work. Use for GitLab project discovery, not local filesystem search or GitHub repositories.
gitlab-work-items
Find, inspect, create or update GitLab issues and other work items, including explicitly requested planning follow-ups. Use for GitLab work items, not GitHub issues, and do not infer permission to publish from a request to brainstorm.
create-handoff
Create a bounded handoff for another agent or person on the board with handoffsend, after confirming the recipient, the request and the sensitivity with the user.
pm
Project Manager skill. One orchestrator session drives eight subagent roles -- planner, plan-reviewer, doer, reviewer, deployer, integ-test-runner, ci-watcher, harvester -- through cycles of Plan, Develop, Test, and Harvest across one or more parallel tracks in isolated git worktrees, running each task on a…
close-handoff
Close or park a handoff with handoffupdatestatus, marking it completed or blocked as its recipient, or cancelled as its sender while it is still queued.
review-handoffs
Review the user's handoff inbox with handoffinbox and read a single handoff with its append-only event history with handoffget.