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 rockscy/solo-skills --skill email-customergit clone --depth 1 https://github.com/rockscy/solo-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/rockscy/solo-skills/email-customer)<a href="https://agentmods.dev/skills/rockscy/solo-skills/email-customer"><img src="https://agentmods.dev/badge/skills/rockscy/solo-skills/email-customer/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/rockscy/solo-skills/email-customer"><img src="https://agentmods.dev/badge/skills/rockscy/solo-skills/email-customer.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.00071 | $0.01413 |
| Opus 5 | $0.00036 | $0.00707 |
| Sonnet 5 | $0.00014 | $0.00283 |
| Haiku 4.5 | $0.00007 | $0.00141 |
Grade A, and why
email-customer 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 11d 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 — 142 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Email Customer / 客户邮件回复
When to use
- The dev is replying to a real customer (paying or potential).
- The reply needs to be polite, firm, and short — not corporate, not groveling.
- The situation is awkward: refund, dispute, scope creep, deadline push, complaint.
When NOT to use
- A routine inquiry ("what's the price?") — answer directly, no skill needed.
- An abusive or harassing message — those need a moderation policy, not a charming reply. Suggest: don't engage; if needed, refund and ban.
- A legal threat — stop. Don't reply via skill. Suggest the user consult a lawyer first.
Principles
A good solo-founder reply has four properties:
- Acknowledge the specific concern (not "I understand your frustration").
- State the decision plainly in one sentence, near the top.
- Give one reason, no more. (Listing reasons reads as defensive.)
- Offer a concrete next step — a workaround, a partial refund, a deadline, a closing line.
Avoid:
- "I'm sorry you feel that way" — not an apology, reads as dismissive.
- "Per our policy" — bureaucratic, hides the human behind procedure.
- Hedging multiple times in one email ("we might be able to possibly consider…").
- More than ~120 words. If it needs more, it's a phone call or a doc.
Output format
Always produce:
- Subject: (one short line, no "Re: Re:")
- Body: (≤120 words, plain text, no signature)
- Internal note: (one line for the dev — what they should do operationally after sending, e.g. "issue partial refund of $19", "add to email block list")
Worked examples
Example 1: Refund request after 60 days, policy is 30
Customer:
"I bought the annual plan 60 days ago and barely used it. Can I get a refund?"
Output:
Subject: Refund on your annual plan
Body:
Hi ,
Refunds on annual plans are limited to the first 30 days, so a full refund isn't something I can offer here.
What I can do: switch you to month-to-month and refund the unused months as account credit, or process a 50% refund on the remaining time. Either is fine — let me know which you'd prefer.
—
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.
- 11d ago First seen · 142 lines · 71 tokens per session scan A d88ac86434d4
email-customer is a skill published in the GitHub repository rockscy/solo-skills (8 stars, last pushed 2mo ago), licensed MIT. It adds 71 tokens to every session and 1,413 once invoked, about $0.0004 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-08-31.
Other skills, from other repositories
dep-auditor
A read-only audit of a project’s third-party packages for known security issues, version health, and license facts. It uses the versions actually selected by lockfiles, which record the exact packages installed, rather than relying only on version ranges.
github-actions-gen
A guide for creating or updating GitHub Actions workflows, which are automated jobs that test, build, release, or deploy code. It first examines the real project before choosing commands, runtimes, caches, and permissions.
api-tester
A tool for creating and checking API tests from the real API contract and implementation. An API is the agreed way that software sends requests and receives responses.
skill-curator
A Chinese-language evaluator for deciding whether developer tools and agent resources are suitable for a curated collection. It checks real repositories, installation paths, activity, duplicates, and security boundaries using evidence.
env-manager
An environment-variable manager for project settings stored outside the code, often in .env files. It checks variable definitions and usage while keeping secret values out of reports and terminal output.
error-translator
A Chinese-language assistant that translates English programming errors and explains what they mean. It covers common errors from languages and frameworks including Python, JavaScript, TypeScript, Java, and others.