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 Davidhevesi/marketing-skills-repo --skill client-communicationgit clone --depth 1 https://github.com/Davidhevesi/marketing-skills-repoWrote 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/davidhevesi/marketing-skills-repo/client-communication)<a href="https://agentmods.dev/skills/davidhevesi/marketing-skills-repo/client-communication"><img src="https://agentmods.dev/badge/skills/davidhevesi/marketing-skills-repo/client-communication/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/davidhevesi/marketing-skills-repo/client-communication"><img src="https://agentmods.dev/badge/skills/davidhevesi/marketing-skills-repo/client-communication.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.00036 | $0.05261 |
| Opus 5.5 | $0.00014 | $0.02104 |
| Sonnet 5.5 | $0.00007 | $0.01052 |
| Haiku 4.5 | $0.00004 | $0.00526 |
Grade A, and why
client-communication 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 2mo 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 — 627 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Client Communication
You help users write the communications that happen throughout the client relationship — from the first proposal to the final follow-up. This skill covers proposals, follow-ups, project updates, review requests, testimonial collection, and re-engagement of past clients. Good client communication is not just professional courtesy — it's a retention and referral engine.
Works for any service business, agency, freelancer, consultant, or local business with an ongoing client relationship.
Before You Start
Check for Context
Look for a Business Context document and a Brand Voice Guide in the project knowledge files.
If both exist: Read them before writing anything. The business type, services, pricing, client profile, brand voice mechanics, and how they refer to customers ("clients" vs. "customers" vs. "members") are all there. Client communication that matches the brand voice feels like a natural extension of the relationship — not a template.
If only Business Context exists: Use it. Apply Section 8 (Brand Voice) for tone guidance.
If neither exists: Say — "To write client communications that sound like you and fit your relationships, I need some context. Do you have a Business Context document in this project? If not, tell me: what type of business is this, how formal or informal is your client relationship, and what's the communication specifically for?"
Workflow
Step 1: Identify the Task
Client communication spans the full relationship lifecycle. Get specific.
What are we writing?
- Proposal (new project or engagement)
- Follow-up (after a proposal, after a meeting, after no response)
- Project update (milestone, check-in, or status communication)
- Scope change or issue communication
- Project completion / handoff
- Review request (ask for a Google/platform review)
- Testimonial request (ask for a quote or case study)
- Re-engagement (reach out to a past client who's gone quiet)
- Referral ask (ask a happy client to refer others)
- General client-facing template (intake form, onboarding email, etc.)
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.
- 2mo ago First seen · 627 lines · 36 tokens per session scan A b9b8f6b33063
client-communication is a skill published in the GitHub repository Davidhevesi/marketing-skills-repo (6 stars, last pushed 7mo ago), licensed MIT. It adds 36 tokens to every session and 5,261 once invoked, about $0.0001 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.
client-communication compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| client-communicationDavidhevesi/marketing-skills-repo | Skill | 6 | 7mo ago | MIT | A | 36 | Claude Code, Codex |
| imagegenopenai/codex | Skill | 133k | yesterday | Apache-2.0 | A | 113 | Codex |
| playwright-climicrosoft/playwright | Skill | 99k | yesterday | Apache-2.0 | A | 19 | Claude Code |
| local-ai-agentsmicrosoft/ai-agents-for-beginners | Skill | 79k | 4d ago | MIT | A | 200 | Claude Code, Codex |
| systematic-debuggingobra/superpowers | Skill | 313k | 3d ago | MIT | A | 21 | Claude Code |
| next-cache-components-adoptionvercel/next.js | Skill | 143k | yesterday | MIT | A | 95 | Claude Code |
| next-partial-prefetching-adoptionvercel/next.js | Skill | 143k | yesterday | MIT | A | 103 | Claude Code |