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/draft-followupWrote 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/draft-followup)<a href="https://agentmods.dev/commands/arise-ai-group/lead-management-plugin/draft-followup"><img src="https://agentmods.dev/badge/commands/arise-ai-group/lead-management-plugin/draft-followup.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.00880 |
| Opus 5 | $0.00000 | $0.00440 |
| Sonnet 5 | $0.00000 | $0.00176 |
| Haiku 4.5 | $0.00000 | $0.00088 |
Grade A, and why
draft-followup 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 — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/draft-followup
If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.md.
Draft a personalized follow-up email after a sales call. Paste your notes or transcript, get a ready-to-send follow-up plus an internal team summary.
Usage
/draft-followup
Then paste your call notes, transcript, or describe what happened.
How It Works
┌─────────────────────────────────────────────────────────────────┐
│ DRAFT FOLLOW-UP │
├─────────────────────────────────────────────────────────────────┤
│ STANDALONE (always works) │
│ ✓ Paste notes, transcript, or describe the call │
│ ✓ Extract pain points, objections, next steps, budget signals │
│ ✓ Draft personalized follow-up email (150-250 words) │
│ ✓ Generate internal team summary │
│ ✓ CRM update recommendations │
├─────────────────────────────────────────────────────────────────┤
│ SUPERCHARGED (when you connect your tools) │
│ + ~~conversation intelligence: Pull transcript automatically │
│ + ~~CRM: Update record, advance pipeline, log activity │
│ + ~~chat: Route draft for team review with approve/send │
│ + ~~email: Send approved follow-up directly │
└─────────────────────────────────────────────────────────────────┘
What I Need From You
Option 1: Paste a transcript Full transcripts from Fireflies, Gong, Zoom, or any other tool. I'll extract everything.
Option 2: Paste your notes Bullet points, rough notes, stream of consciousness — whatever you jotted down during the call.
Option 3: Describe the call "Had a discovery call with Acme Corp. Their VP Ops is drowning in manual onboarding — team of 30, spending 20 hours/week on data entry. Budget around $5k/month. They want to start next month."
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 · 130 lines · 0 tokens per session scan A f453858ad091
draft-followup 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 880 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.