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 pipeline-reportgit 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/pipeline-report)<a href="https://agentmods.dev/skills/theyahia/wwmcp/pipeline-report"><img src="https://agentmods.dev/badge/skills/theyahia/wwmcp/pipeline-report/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/pipeline-report"><img src="https://agentmods.dev/badge/skills/theyahia/wwmcp/pipeline-report.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.00024 | $0.00634 |
| Opus 5.5 | $0.00010 | $0.00254 |
| Sonnet 5.5 | $0.00005 | $0.00127 |
| Haiku 4.5 | $0.00002 | $0.00063 |
Grade A, and why
pipeline-report 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.
What it actually says
/pipeline-report — Состояние воронки
Алгоритм
list_pipelines(без аргументов) — все воронки и их этапы. Отсюда берутся pipeline_id и status_id; без них цифры по этапам не собрать.list_leads(pipeline_id, statuses, page, limit до 250, query, with) — сделки воронки. Пройди страницы, пока выдача не кончится.- Сгруппируй сделки по этапам: количество и сумма price на каждом.
- Найди застрявшие:
list_events(entity: leads, entity_id, type, page, limit до 100) — когда сделка последний раз двигалась. Нет событий давно = сделка стоит. - Открой проблемные карточки:
get_lead(lead_id, with) — с вложенными контактами и причиной отказа. - Проверь, есть ли по ним задачи:
list_tasks(entity_type: leads, entity_id, is_completed: false, responsible_user_id). - Если по сделкам нет ни одной активной задачи — это главный вывод отчёта: воронка без follow-up.
- Имена ответственных и справочники аккаунта —
get_account.
Важно
- Считай сумму только по тем сделкам, которые реально выгрузил:
list_leadsотдаёт максимум 250 за страницу, оборванная выгрузка даёт заниженный итог. Скажи, сколько страниц прошёл. - status_id уникален внутри воронки — не сравнивай этапы разных воронок по номеру.
- Ничего не меняй в этом скилле. Перенос сделки —
update_lead, но только по отдельному явному запросу пользователя.
Формат ответа
## Воронка «Продажи» (pipeline_id 3311)
Сделок: 148 · Сумма: 21 400 000 ₽ (выгружено 148 из 148)
| Этап | Сделок | Сумма |
|------|--------|-------|
| Первичный контакт | 61 | 6 100 000 ₽ |
| Переговоры | 44 | 9 800 000 ₽ |
| Счёт выставлен | 28 | 4 200 000 ₽ |
### Застрявшие (нет движения >14 дней)
1. Сделка 88123 «ООО Ромашка» — 850 000 ₽ — Переговоры — активных задач нет
Примеры
/pipeline-report
/pipeline-report Продажи
/pipeline-report покажи застрявшие сделки
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 · 50 lines · 24 tokens per session scan A 5fa1c5beaf57
pipeline-report is a skill published in the GitHub repository theYahia/WWmcp (36 stars, last pushed 1mo ago), licensed MIT. It adds 24 tokens to every session and 634 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.
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.
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…