response-drafting

response-drafting is a skill for Claude Code from fergupa/claude_plugins. It costs 47 tokens per session (2,355 once invoked), scanned A, a copy of response-drafting, Apache-2.0.

A writing aid for composing customer-facing replies to tickets, outages, bug reports, feature requests, and escalations. It adapts the tone and detail to the situation and communication channel.

In plain words
What is it for?
Use it to draft support emails, incident updates, escalation replies, and responses to customer feedback.
Why use it?
It helps turn difficult or sensitive situations into clear, honest responses with empathy and a concrete next step.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the customer-support plugin — 5 skills, 5 commands shipped together

Good fit Use it to draft support emails, incident updates, escalation replies, and responses to customer feedback.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/fergupa/claude_plugins/response-drafting
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add fergupa/claude_plugins --skill response-drafting
Clone the repo
git clone --depth 1 https://github.com/fergupa/claude_plugins

Made for: Claude Code.

Or install customer-support, the plugin that ships this one along with the rest of its 5 skills, 5 commands.

Wrote 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.

agentmods badge for response-drafting

README.md
[![agentmods](https://agentmods.dev/badge/skills/fergupa/claude_plugins/response-drafting/github.svg)](https://agentmods.dev/skills/fergupa/claude_plugins/response-drafting)
Your own site
<a href="https://agentmods.dev/skills/fergupa/claude_plugins/response-drafting"><img src="https://agentmods.dev/badge/skills/fergupa/claude_plugins/response-drafting/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.

agentmods 80×15 button for response-drafting

Your own site · 80×15
<a href="https://agentmods.dev/skills/fergupa/claude_plugins/response-drafting"><img src="https://agentmods.dev/badge/skills/fergupa/claude_plugins/response-drafting.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 47 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,355 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 100% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00047 $0.02355
Opus 5 $0.00023 $0.01177
Sonnet 5 $0.00009 $0.00471
Haiku 4.5 $0.00005 $0.00235

Measured 9d ago against content hash e172bf013a0c, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

response-drafting 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.

Origin

This is a copy

100% identical to response-drafting — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

customer-support/skills/response-drafting/SKILL.md · 303 lines

How it starts

The opening of the file, as written. The whole thing — 303 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Response Drafting Skill

You are an expert at drafting professional, empathetic, and effective customer-facing communications. You adapt tone, structure, and content based on the situation, relationship stage, stakeholder level, and communication channel.

Customer Communication Best Practices

Core Principles

  1. Lead with empathy: Acknowledge the customer's situation before jumping to solutions
  2. Be direct: Get to the point — customers are busy. Bottom-line-up-front.
  3. Be honest: Never overpromise, never mislead, never hide bad news in jargon
  4. Be specific: Use concrete details, timelines, and names — avoid vague language
  5. Own it: Take responsibility when appropriate. "We" not "the system" or "the process"
  6. Close the loop: Every response should have a clear next step or call to action
  7. Match their energy: If they're frustrated, be empathetic first. If they're excited, be enthusiastic.

Response Structure

For most customer communications, follow this structure:

1. Acknowledgment / Context (1-2 sentences)
   - Acknowledge what they said, asked, or are experiencing
   - Show you understand their situation

2. Core Message (1-3 paragraphs)
   - Deliver the main information, answer, or update
   - Be specific and concrete
   - Include relevant details they need

3. Next Steps (1-3 bullets)
   - What YOU will do and by when
   - What THEY need to do (if anything)
   - When they'll hear from you next

4. Closing (1 sentence)
   - Warm but professional sign-off
   - Reinforce you're available if needed

Length Guidelines

  • Chat/IM: 1-4 sentences. Get to the point immediately.
  • Support ticket response: 1-3 short paragraphs. Structured and scannable.
  • Email: 3-5 paragraphs max. Respect their inbox.
  • Escalation response: As long as needed to be thorough, but well-structured with headers.
  • Executive communication: Shorter is better. 2-3 paragraphs max. Data-driven.

Tone and Style Guidelines

Read the full file on GitHub · 303 lines

Changes

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.

  1. 9d ago First seen · 303 lines · 47 tokens per session scan A e172bf013a0c

Subscribe to this mod's changes

response-drafting is a skill published in the GitHub repository fergupa/claude_plugins (2 stars, last pushed 7mo ago), licensed Apache-2.0. It adds 47 tokens to every session and 2,355 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to response-drafting, differing in 0 lines, and is treated as a copy.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens