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.
npx skills add w95/awesome-claude-corporate-skills --skill response-draftinggit clone --depth 1 https://github.com/w95/awesome-claude-corporate-skillsWrote 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/skills/w95/awesome-claude-corporate-skills/response-drafting)<a href="https://agentmods.dev/skills/w95/awesome-claude-corporate-skills/response-drafting"><img src="https://agentmods.dev/badge/skills/w95/awesome-claude-corporate-skills/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.
<a href="https://agentmods.dev/skills/w95/awesome-claude-corporate-skills/response-drafting"><img src="https://agentmods.dev/badge/skills/w95/awesome-claude-corporate-skills/response-drafting.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.00047 | $0.02355 |
| Opus 5 | $0.00023 | $0.01177 |
| Sonnet 5 | $0.00009 | $0.00471 |
| Haiku 4.5 | $0.00005 | $0.00235 |
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.
Copies of this mod
1 near-identical copy found in the catalogue:
- response-drafting — 100% identical, 0 lines differ
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
- Lead with empathy: Acknowledge the customer's situation before jumping to solutions
- Be direct: Get to the point — customers are busy. Bottom-line-up-front.
- Be honest: Never overpromise, never mislead, never hide bad news in jargon
- Be specific: Use concrete details, timelines, and names — avoid vague language
- Own it: Take responsibility when appropriate. "We" not "the system" or "the process"
- Close the loop: Every response should have a clear next step or call to action
- 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
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 · 303 lines · 47 tokens per session scan A e172bf013a0c
response-drafting is a skill published in the GitHub repository w95/awesome-claude-corporate-skills (198 stars, last pushed 6mo ago), licensed MIT. 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. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
design-por-referencia
Use when a landing page, marketing site, or hero section looks generic/AI-made ("cara de vibe coding") and needs a $10k-agency-level redesign, or when building a new landing from scratch. Triggers - "o site ficou com cara de IA", "quero uma landing premium", "redesenha a landing", "faz o site baseado em [site de…
lighthouse-95
Use when a website must score 95+ in every Lighthouse category (Performance, Accessibility, Best Practices, SEO), when scores are stuck below target, or when diagnosing poor FCP, LCP, TBT, or CLS on a deployed site.
seo-validate
SEO validator: meta/OG, Schema.org, hreflang, Core Web Vitals, crawlability. Triggers: SEO, meta tags, Schema.org, hreflang, LCP, INP, CLS, Core Web Vitals, sitemap, crawlability.
debug
Systematic debugging via logs, health checks, hypothesis-driven investigation. Triggers: debug, error, trace root cause, fix bug, reproduce symptom, investigation.
pr
Creates GitHub PR after pre-flight checks (lint/typecheck/tests), structured summary from commits. Triggers: pr, pull request, create PR, ready to merge.
research-mastery
Hierarchical retrieval: KB → MCP/Context7 → web. Triggers: research, fact-check, verify, synthesize, cross-reference, multi-source, cite sources.