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/capture-leadWrote 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/capture-lead)<a href="https://agentmods.dev/commands/arise-ai-group/lead-management-plugin/capture-lead"><img src="https://agentmods.dev/badge/commands/arise-ai-group/lead-management-plugin/capture-lead.svg" alt="Measured on agentmods" 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.00785 |
| Opus 5 | $0.00000 | $0.00392 |
| Sonnet 5 | $0.00000 | $0.00157 |
| Haiku 4.5 | $0.00000 | $0.00078 |
Grade A, and why
capture-lead 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 7d 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 — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/capture-lead
If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.md.
Quickly capture a new lead from any source — paste their info, describe how you met them, or import a batch of contacts.
Usage
/capture-lead
Then provide the lead's information (name, email, company, context).
How It Works
┌─────────────────────────────────────────────────────────────────┐
│ CAPTURE LEAD │
├─────────────────────────────────────────────────────────────────┤
│ STANDALONE (always works) │
│ ✓ Parse lead info from whatever you provide │
│ ✓ AI qualification scoring (Hot / Warm / Cold) │
│ ✓ Structured lead card for your team │
│ ✓ Auto-reply email draft │
│ ✓ Recommended next steps based on score │
├─────────────────────────────────────────────────────────────────┤
│ SUPERCHARGED (when you connect your tools) │
│ + ~~CRM: Create record, check duplicates │
│ + ~~chat: Post lead card to team channel │
│ + ~~email: Send auto-reply acknowledgment │
└─────────────────────────────────────────────────────────────────┘
What I Need From You
Option 1: Quick capture Just tell me the basics: "Sarah Chen, [email protected], met her at TechCrunch Disrupt, she runs ops at a 50-person fintech."
Option 2: Paste form data If you have form submission data, paste it and I'll parse all fields.
Option 3: Batch import Paste a CSV, bullet list, or table of contacts. I'll process each one, deduplicate, and score them all.
Option 4: Describe the interaction "Just got off a call with someone from Acme Corp — they're looking for automation help, seemed very interested, team of about 30 people."
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.
- 7d ago First seen · 122 lines · 0 tokens per session scan A 90b9c8348bb0
capture-lead 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 785 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.