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 mostafa-drz/claude-skills --skill respond-to-messagegit clone --depth 1 https://github.com/mostafa-drz/claude-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/mostafa-drz/claude-skills/respond-to-message)<a href="https://agentmods.dev/skills/mostafa-drz/claude-skills/respond-to-message"><img src="https://agentmods.dev/badge/skills/mostafa-drz/claude-skills/respond-to-message/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/mostafa-drz/claude-skills/respond-to-message"><img src="https://agentmods.dev/badge/skills/mostafa-drz/claude-skills/respond-to-message.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.00075 | $0.02247 |
| Opus 5.5 | $0.00030 | $0.00899 |
| Sonnet 5.5 | $0.00015 | $0.00449 |
| Haiku 4.5 | $0.00007 | $0.00225 |
Grade A, and why
respond-to-message 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 — 255 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Respond to Message
Craft responses to messages in your voice, matched to the platform. Copies to clipboard for pasting.
Preferences
Before starting, use the Read tool to read ~/.claude/skills/respond-to-message/preferences.md. If the file does not exist, treat as "no preferences set" and use defaults.
Tone Profile
Use the Read tool to read ~/.claude/skills/respond-to-message/reference/tone-profile.md. If it does not exist, fall back to preferences tone keywords. If neither exists, ask the user to describe their tone.
Platform Context
Use Glob to check which platform files exist at ~/.claude/skills/respond-to-message/reference/platforms/*.md. For the active platform, read its context file. If no file exists for the requested platform, use sensible defaults for that platform's conventions.
Command routing
Check $ARGUMENTS:
help→ display help then stopconfig→ interactive setup then stopreset→ delete~/.claude/skills/respond-to-message/preferences.md, confirm, stoptone→ open tone profile editing flow then stop- anything else (including empty) → run the skill
Help
Respond to Message — Craft replies in your voice, matched to the platform
Usage:
/respond-to-message <platform> Craft a response (then paste the message)
/respond-to-message Auto-detect platform or ask
/respond-to-message --refine Re-draft the last response with feedback
/respond-to-message --formal Override tone to more formal
/respond-to-message --casual Override tone to more casual
/respond-to-message config Set up tone, platforms, and context
/respond-to-message tone Edit your tone profile with examples
/respond-to-message reset Clear preferences
/respond-to-message help This help
Platforms: linkedin, slack, gmail, teams, whatsapp, twitter, generic
Examples:
/respond-to-message linkedin Then paste the LinkedIn message in chat
/respond-to-message slack Then paste the Slack message + optional draft
/respond-to-message gmail --formal Reply to an email with formal tone override
Current preferences:
(from preferences.md or defaults)
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 Changed · +2 lines ad449a8f8704
- 1mo ago First seen · 253 lines · 75 tokens per session scan A fc5bdf593a85
respond-to-message is a skill published in the GitHub repository mostafa-drz/claude-skills (4 stars, last pushed yesterday), licensed MIT. It adds 75 tokens to every session and 2,247 once invoked, about $0.0003 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 skills, from other repositories
skill-builder
Automatically detect source types and build AI skills using Skill Seekers. Use when the user wants to create skills from documentation, repos, PDFs, videos, or other knowledge sources.
rudder-data-graphs
Produces Data Graph YAML from RETL sources for Audiences. Use when designing Data Graphs, mapping RETL to entities/events, or assessing customer fit for Audiences.
rudder-typer-workflow
Generates type-safe SDKs (Swift/Kotlin) from tracking plans with compile-time validation. Use when generating type-safe event tracking code from tracking plans using RudderTyper.
rudder-instrumentation-planning
Designs event taxonomies and instrumentation strategies from business requirements. Use when designing event taxonomy from scratch or restructuring existing instrumentation strategy.
rudder-instrumentation-debugging
Diagnoses and fixes validation errors, schema issues, and instrumentation problems. Use when debugging validation errors, schema issues, or instrumentation problems.
rudder-ai-events-verify
Verifies RudderStack AI events locally: captures what an instrumented app or MCP server sends, validates it against the AI events v0.3 schema, and checks joins, counts, identity and content. Use when testing AI events, or when AI or MCP events look wrong or missing.