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/fergupa/claude_pluginsnpx agentmods add commands/fergupa/claude_plugins/draft-responseWrote 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/fergupa/claude_plugins/draft-response)<a href="https://agentmods.dev/commands/fergupa/claude_plugins/draft-response"><img src="https://agentmods.dev/badge/commands/fergupa/claude_plugins/draft-response/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/fergupa/claude_plugins/draft-response"><img src="https://agentmods.dev/badge/commands/fergupa/claude_plugins/draft-response.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.00012 | $0.01167 |
| Opus 5.5 | $0.00005 | $0.00467 |
| Sonnet 5.5 | $0.00002 | $0.00233 |
| Haiku 4.5 | $0.00001 | $0.00117 |
Grade A, and why
draft-response 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 1mo 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 — 155 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Draft Response
If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.md.
Draft a professional, customer-facing response tailored to the situation, customer relationship, and communication context.
Usage
/draft-response <context about the customer question, issue, or request>
Examples:
/draft-response Acme Corp is asking when the new dashboard feature will ship/draft-response Customer escalation — their integration has been down for 2 days/draft-response Responding to a feature request we won't be building/draft-response Customer hit a billing error and wants a resolution ASAP
Workflow
1. Understand the Context
Parse the user's input to determine:
- Customer: Who is the communication for? Look up account context if available.
- Situation type: Question, issue, escalation, announcement, negotiation, bad news, good news, follow-up
- Urgency: Is this time-sensitive? How long has the customer been waiting?
- Channel: Email, support ticket, chat, or other (adjust formality accordingly)
- Relationship stage: New customer, established, frustrated/escalated
- Stakeholder level: End user, manager, executive, technical, business
2. Research Context
Gather relevant background from available sources:
~~email:
- Previous correspondence with this customer on this topic
- Any commitments or timelines previously shared
- Tone and style of the existing thread
~~chat:
- Internal discussions about this customer or topic
- Any guidance from product, engineering, or leadership
- Similar situations and how they were handled
~~CRM (if connected):
- Account details and plan level
- Contact information and key stakeholders
- Previous escalations or sensitive issues
~~support platform (if connected):
- Related tickets and their resolution
- Known issues or workarounds
- SLA status and response time commitments
~~knowledge base:
- Official documentation or help articles to reference
- Product roadmap information (if shareable)
- Policy or process documentation
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.
- 1mo ago First seen · 155 lines · 12 tokens per session scan A 3a81a31f65dc
draft-response is a command published in the GitHub repository fergupa/claude_plugins (2 stars, last pushed 8mo ago), licensed Apache-2.0. It adds 12 tokens to every session and 1,167 once invoked, about $0.0000 per session on Opus 5.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-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.
speckit.bug.fix
Apply the remediation from a bug assessment and record what was changed.