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 deal-pipelinegit 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/deal-pipeline)<a href="https://agentmods.dev/skills/theyahia/wwmcp/deal-pipeline"><img src="https://agentmods.dev/badge/skills/theyahia/wwmcp/deal-pipeline/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/deal-pipeline"><img src="https://agentmods.dev/badge/skills/theyahia/wwmcp/deal-pipeline.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.00700 |
| Opus 5 | $0.00012 | $0.00350 |
| Sonnet 5 | $0.00005 | $0.00140 |
| Haiku 4.5 | $0.00002 | $0.00070 |
Grade A, and why
deal-pipeline 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.
How it starts
The opening of the file, as written. The whole thing — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/deal-pipeline — Deal pipeline review
Algorithm
- Call
get_dealswith optional filter_status (account-specific status codes), filter_responsible_id or search, plus limit (max 100). Lists are cursor-paginated: pass the returnednextPageAfterback aspage_afteruntil the list ends. - Call
get_employeesto resolve responsible IDs into names. - Group deals by status and sum amount per group — that is the pipeline picture. Show both count and money; a stage with many small deals is a different problem from one with few large ones.
- Find stalled deals: for the largest ones, call
get_dealwith the deal ID for the full record, thenget_commentswith subject_type = deal and subject_id = that ID. A deal with no recent comment is not being worked. Uselist_clientsorget_clientwhen you need the counterparty behind a deal. - Call
get_projectswith filter_status or search if the user wants to see which delivery projects the won deals feed into. - To add a deal, call
get_deal_programsfirst to find the program_id (the pipeline ID —create_dealrequires it), then callcreate_dealwith name and program_id, plus optionally responsible_id, contact_id, amount and description. Useget_deal_programfor the detail of one pipeline. - To chase a deal, call
create_commentwith subject_type = deal, subject_id and content.
Response format
## Megaplan pipeline
| Stage | Deals | Value |
|-------|-------|-------|
| negotiation | 14 | 4,820,000 ₽ |
| proposal sent | 9 | 2,310,000 ₽ |
| won | 6 | 3,150,000 ₽ |
**Open pipeline**: 7,130,000 ₽ across 23 deals
### Stalled (no comment in 14+ days)
| Deal | Value | Owner | Last activity |
|------|-------|-------|---------------|
| Contract — Romashka | 1,200,000 ₽ | Ivan Petrov | 2026-08-14 |
Notes
- program_id is mandatory for
create_deal. Get it fromget_deal_programs— never guess an ID.update_dealchanges an existing deal without recreating it. - Status codes are account-specific. If a filter returns empty, pull unfiltered and group by whatever status values actually come back.
create_dealtakes the amount asamount+currency; the server wraps it into the v3 Money object. Tool output is a compact summary by default (raw: truefor the API JSON).create_commentnotifies the assignee. Get the text approved before posting.
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 · 66 lines · 23 tokens per session scan A a0fba1e60e4d
deal-pipeline is a skill published in the GitHub repository theYahia/WWmcp (29 stars, last pushed 5d ago), licensed MIT. It adds 23 tokens to every session and 700 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
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…
fleet-sprint-cli
How to launch and supervise apra-fleet's autonomous sprint workflow from the CLI (apra-fleet workflow fleet-sprint) -- the --issue/--members/--branch/--base flag contract, the preconditions to check first, how to launch it as a detached process, and how to watch it via its dashboard. Trigger before running apra-fleet…
auto-sprint-args
How to construct and pass correct arguments to the auto-sprint workflow -- the required issues+branch fields, optional goal/maxcycles/basebranch/requirementsFile, JSON-object (not string) shape, and common launch mistakes. Trigger when preparing to launch or invoke auto-sprint.
jira
Operate Jira Cloud via its REST v3 API — issues, projects, sprints, boards, comments, transitions, JQL search. Use when the user wants to triage, bulk-update, report on, or otherwise interact with Jira programmatically without the MCP server installed.
linear
Query and mutate Linear issues, projects, cycles, teams, workflow states, and comments via its GraphQL API. Use when the user wants to read or change Linear data programmatically — without the MCP server, and without hand-navigating the Linear UI.
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…