Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/Arise-AI-Group/lead-management-pluginnpx agentmods add commands/arise-ai-group/lead-management-plugin/pipeline-reviewWrote 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/commands/arise-ai-group/lead-management-plugin/pipeline-review)<a href="https://agentmods.dev/commands/arise-ai-group/lead-management-plugin/pipeline-review"><img src="https://agentmods.dev/badge/commands/arise-ai-group/lead-management-plugin/pipeline-review/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/commands/arise-ai-group/lead-management-plugin/pipeline-review"><img src="https://agentmods.dev/badge/commands/arise-ai-group/lead-management-plugin/pipeline-review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00000 | $0.01162 |
| Opus 5 | $0.00000 | $0.00581 |
| Sonnet 5 | $0.00000 | $0.00232 |
| Haiku 4.5 | $0.00000 | $0.00116 |
Grade A, and why
pipeline-review 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 10d 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 — 139 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/pipeline-review
If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.md.
Get a snapshot of your sales pipeline — deals by stage, stalled leads, conversion metrics, and action items.
Usage
/pipeline-review
Optionally specify a time range: /pipeline-review for current state, or "pipeline review for January" for a specific period.
How It Works
┌─────────────────────────────────────────────────────────────────┐
│ PIPELINE REVIEW │
├─────────────────────────────────────────────────────────────────┤
│ STANDALONE (always works) │
│ ✓ You describe your current deals, I analyze the pipeline │
│ ✓ Stage distribution and bottleneck identification │
│ ✓ Stalled deal detection with follow-up suggestions │
│ ✓ Conversion rate analysis │
│ ✓ Prioritized action items for the week │
├─────────────────────────────────────────────────────────────────┤
│ SUPERCHARGED (when you connect your tools) │
│ + ~~CRM: Pull all deals, stages, dates, amounts automatically │
│ + ~~chat: Post review summary to team channel │
│ + ~~email: Check for recent lead replies or engagement │
└─────────────────────────────────────────────────────────────────┘
What I Need From You
If CRM is connected: Nothing — I'll pull everything automatically.
If no CRM: Tell me about your current deals:
- Who's in the pipeline
- What stage each deal is at
- How long they've been at that stage
- Any notable activity or blockers
Output
# Pipeline Review — [Date]
## Pipeline Snapshot
| Stage | Count | Total Value | Avg Days in Stage |
|-------|-------|-------------|-------------------|
| New Lead | [N] | — | [N] |
| Contacted | [N] | — | [N] |
| Discovery Scheduled | [N] | $[Value] | [N] |
| Discovery Complete | [N] | $[Value] | [N] |
| Proposal Sent | [N] | $[Value] | [N] |
| Contract Sent | [N] | $[Value] | [N] |
| Contract Signed | [N] | $[Value] | [N] |
| Paid | [N] | $[Value] | — |
**Total pipeline value:** $[Sum of active deals]
**Weighted forecast:** $[Probability-adjusted value]
---
## Stalled Deals (Needs Attention)
| Lead | Company | Stage | Days Stalled | Suggested Action |
|------|---------|-------|-------------|------------------|
| [Name] | [Co] | Discovery Complete | 12 days | Send proposal or re-engage |
| [Name] | [Co] | Contract Sent | 8 days | Check if contract was opened |
| [Name] | [Co] | New Lead | 5 days | First contact overdue |
---
## Conversion Metrics
| Transition | Rate | Avg Time |
|-----------|------|----------|
| Lead → Contacted | [%] | [N] days |
| Contacted → Discovery | [%] | [N] days |
| Discovery → Proposal | [%] | [N] days |
| Proposal → Contract | [%] | [N] days |
| Contract → Signed | [%] | [N] days |
| Signed → Paid | [%] | [N] days |
| **Overall: Lead → Paid** | **[%]** | **[N] days** |
---
## This Week's Action Items
1. **[Priority]** [Action] — [Lead/Company] — [Why now]
2. **[Priority]** [Action] — [Lead/Company] — [Why now]
3. **[Priority]** [Action] — [Lead/Company] — [Why now]
4. **[Priority]** [Action] — [Lead/Company] — [Why now]
5. **[Priority]** [Action] — [Lead/Company] — [Why now]
---
## Revenue Summary
| Metric | This Month | Last Month | Trend |
|--------|-----------|------------|-------|
| Deals closed | [N] | [N] | [↑/↓/→] |
| Revenue collected | $[Amt] | $[Amt] | [↑/↓/→] |
| New leads captured | [N] | [N] | [↑/↓/→] |
| Proposals sent | [N] | [N] | [↑/↓/→] |
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.
- 10d ago First seen · 139 lines · 0 tokens per session scan A 3afe46e5c738
pipeline-review is a command published in the GitHub repository Arise-AI-Group/lead-management-plugin (7 stars, last pushed 7mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,162 tokens. 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-08-31.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.