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/nurture-statusWrote 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/nurture-status)<a href="https://agentmods.dev/commands/arise-ai-group/lead-management-plugin/nurture-status"><img src="https://agentmods.dev/badge/commands/arise-ai-group/lead-management-plugin/nurture-status/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/nurture-status"><img src="https://agentmods.dev/badge/commands/arise-ai-group/lead-management-plugin/nurture-status.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.00925 |
| Opus 5 | $0.00000 | $0.00463 |
| Sonnet 5 | $0.00000 | $0.00185 |
| Haiku 4.5 | $0.00000 | $0.00093 |
Grade A, and why
nurture-status 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 9d 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 — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/nurture-status
If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.md.
Check the status of your nurture sequences — who's being nurtured, what stage they're at, what's due next, and who's showing re-engagement signals.
Usage
/nurture-status
Optionally ask about a specific lead: /nurture-status then "What's the status for Sarah at Acme?"
How It Works
┌─────────────────────────────────────────────────────────────────┐
│ NURTURE STATUS │
├─────────────────────────────────────────────────────────────────┤
│ STANDALONE (always works) │
│ ✓ Review all leads currently in nurture │
│ ✓ Show stage, last touch, and next action for each │
│ ✓ Identify leads showing re-engagement signals │
│ ✓ Flag leads ready to exit nurture │
│ ✓ Draft next nurture email for any lead │
├─────────────────────────────────────────────────────────────────┤
│ SUPERCHARGED (when you connect your tools) │
│ + ~~CRM: Pull all leads in nurture with dates and activity │
│ + ~~chat: Post nurture review to team channel │
│ + ~~email: Check open rates, replies, engagement data │
└─────────────────────────────────────────────────────────────────┘
What I Need From You
If CRM is connected: Nothing — I'll pull all nurture data automatically.
If no CRM: Tell me about the leads you're nurturing:
- Who they are
- What stage they're at (or when you last contacted them)
- Any recent activity
Output
# Nurture Status — [Date]
## Active Nurture Pipeline
| Lead | Company | Stage | Last Touch | Next Action | Due |
|------|---------|-------|-----------|-------------|-----|
| [Name] | [Co] | Stage 1 (Day 3) | [Date] | Value-add email | [Date] |
| [Name] | [Co] | Stage 2 (Day 7) | [Date] | Deeper insight | [Date] |
| [Name] | [Co] | Stage 3 (Day 14) | [Date] | Check-in | Today |
| [Name] | [Co] | Stage 4 (Day 30) | [Date] | Re-engagement | [Date] |
| [Name] | [Co] | Stage 5 (60+) | [Date] | Quarterly touch | [Date] |
**Total in nurture:** [N] leads
---
## Needs Action Today
- **[Name]** ([Company]) — Stage 3 check-in due today
- **[Name]** ([Company]) — Stage 2 deeper insight due today
---
## Re-Engagement Signals
- **[Name]** — Opened Stage 1 email 3 times in 2 days → Consider calling
- **[Name]** — Visited website after Stage 2 email → Warm signal
---
## Ready to Exit
- **[Name]** — Replied to Stage 3 → Route to team for follow-up
- **[Name]** — Booked meeting → Move to discovery prep
- **[Name]** — No opens on 3 emails, 60+ days → Suggest moving to dormant
---
## Summary
| Metric | Count |
|--------|-------|
| Total in nurture | [N] |
| Due this week | [N] |
| Showing engagement | [N] |
| Recommend exit | [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.
- 9d ago First seen · 117 lines · 0 tokens per session scan A 3b0a7b063e44
nurture-status 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 925 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.
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.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.