deal-pipeline

deal-pipeline is a skill for Claude Code from theYahia/WWmcp. It costs 23 tokens per session (700 once invoked), scanned A, original, MIT.

A deal-pipeline review for Megaplan, a customer and sales management system. It groups deals by stage, value, and responsible employee.

In plain words
What is it for?
Use it to review pipeline value, find stalled deals, identify the people responsible, inspect related customers or projects, and add a new deal.
Why use it?
It shows where potential sales are concentrated and which important deals may have stopped moving. It avoids relying on a simple list without totals or recent activity.

Skill for Claude Code

Written for Claude Code: argument-hint in frontmatter.

Good fit Use it to review pipeline value, find stalled deals, identify the people responsible, inspect related customers or projects, and add a new deal.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/theyahia/wwmcp/deal-pipeline
Install

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.

Any agent
npx skills add theYahia/WWmcp --skill deal-pipeline
Clone the repo
git clone --depth 1 https://github.com/theYahia/WWmcp

Made for: Claude Code.

Wrote 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.

agentmods badge for deal-pipeline

README.md
[![agentmods](https://agentmods.dev/badge/skills/theyahia/wwmcp/deal-pipeline/github.svg)](https://agentmods.dev/skills/theyahia/wwmcp/deal-pipeline)
Your own site
<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.

agentmods 80×15 button for deal-pipeline

Your own site · 80×15
<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>
Per session 23 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 700 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured 6d ago against content hash a0fba1e60e4d, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

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.

servers/megaplan/.claude/skills/deal-pipeline/SKILL.md · 66 lines

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

  1. Call get_deals with optional filter_status (account-specific status codes), filter_responsible_id or search, plus limit (max 100). Lists are cursor-paginated: pass the returned nextPageAfter back as page_after until the list ends.
  2. Call get_employees to resolve responsible IDs into names.
  3. 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.
  4. Find stalled deals: for the largest ones, call get_deal with the deal ID for the full record, then get_comments with subject_type = deal and subject_id = that ID. A deal with no recent comment is not being worked. Use list_clients or get_client when you need the counterparty behind a deal.
  5. Call get_projects with filter_status or search if the user wants to see which delivery projects the won deals feed into.
  6. To add a deal, call get_deal_programs first to find the program_id (the pipeline ID — create_deal requires it), then call create_deal with name and program_id, plus optionally responsible_id, contact_id, amount and description. Use get_deal_program for the detail of one pipeline.
  7. To chase a deal, call create_comment with 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 from get_deal_programs — never guess an ID. update_deal changes 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_deal takes the amount as amount + currency; the server wraps it into the v3 Money object. Tool output is a compact summary by default (raw: true for the API JSON).
  • create_comment notifies the assignee. Get the text approved before posting.

Read the full file on GitHub · 66 lines

Changes

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.

  1. 6d ago First seen · 66 lines · 23 tokens per session scan A a0fba1e60e4d

Subscribe to this mod's changes

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.

Related

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…

Apra-Labs/apra-fleet · 120 tokens

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…

Apra-Labs/apra-fleet · 85 tokens

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.

Apra-Labs/apra-fleet · 61 tokens

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.

mnlt/teleport · 57 tokens

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.

mnlt/teleport · 54 tokens

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…

ProjAnvil/MindForge · 69 tokens