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 bguivarch/skillforge --skill client-emailgit clone --depth 1 https://github.com/bguivarch/skillforgeWrote 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/bguivarch/skillforge/client-email)<a href="https://agentmods.dev/skills/bguivarch/skillforge/client-email"><img src="https://agentmods.dev/badge/skills/bguivarch/skillforge/client-email/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/bguivarch/skillforge/client-email"><img src="https://agentmods.dev/badge/skills/bguivarch/skillforge/client-email.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.00008 | $0.00334 |
| Opus 5.5 | $0.00003 | $0.00134 |
| Sonnet 5.5 | $0.00002 | $0.00067 |
| Haiku 4.5 | $0.00001 | $0.00033 |
Grade A, and why
client-email 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.
What it actually says
Client Email Writer
Craft professional, effective emails for client communication.
Email Types I Can Help With
Project Updates
- Progress reports and milestones
- Deliverable notifications
- Timeline changes and delays
- Status summaries
Proposals & Quotes
- Service proposals
- Price quotations
- Scope of work descriptions
- Contract follow-ups
Relationship Management
- Initial introductions
- Thank you messages
- Check-in emails
- Re-engagement outreach
Issue Resolution
- Addressing concerns professionally
- Apology and resolution emails
- Clarification requests
- Feedback responses
How to Use
- Tell me the email type (update, proposal, issue, etc.)
- Provide context about the client relationship
- Share the key points you want to convey
- Mention any specific tone requirements
What I'll Provide
- Subject line: Clear and actionable
- Email body: Professional and concise
- Call to action: Clear next steps
- Alternative versions: If requested (shorter, more formal, etc.)
Tone Options
- Formal: For new clients or sensitive matters
- Professional-friendly: Balanced warmth with professionalism
- Casual-professional: For established relationships
Best Practices I Follow
- Keep emails concise and scannable
- Lead with the most important information
- Use clear, jargon-free language
- Include specific calls to action
- Maintain a positive, solution-oriented tone
- Proofread for typos and clarity
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 First seen · 64 lines · 8 tokens per session scan A 7bb69d315757
client-email is a skill published in the GitHub repository bguivarch/skillforge (3 stars, last pushed 8mo ago), licensed Apache-2.0. It adds 8 tokens to every session and 334 once invoked, about $0.0000 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
offensive-vuln-classes
Exploit development curriculum covering core vulnerability classes with real-world CVE case studies: stack/heap buffer overflows, use-after-free, integer overflows, format strings, type confusion, and race conditions. Use when learning or teaching vuln classes, researching specific CVE patterns, or building exploit…
offensive-edr-evasion
EDR evasion offensive checklist: hook unhooking (user/kernel), direct syscalls, PPID spoofing, process injection variants, AMSI bypass, ETW patching, memory encryption, and behavior-based evasion. Use when planning EDR bypass during red team engagements or researching AV/EDR evasion techniques.
offensive-mitigations
Security mitigation reference and bypass catalog: ASLR, DEP/NX, RELRO, stack canaries, CFI, sandboxing, seccomp. Covers both detection of enabled mitigations and known bypass techniques. Use when assessing target hardening or planning exploit mitigation bypasses.
offensive-initial-access
Initial access techniques checklist: phishing (spear/smishing), credential stuffing, exposed service exploitation, supply chain attacks, watering hole, VPN/RDP brute force, public-facing application exploitation. Maps to MITRE ATT&CK TA0001. Use when planning initial access phases of red team engagements.
offensive-exploit-development
Exploit development operational guide: environment setup, debugging workflow, PoC development lifecycle, writing reliable exploits, using pwntools/pwndbg, heap exploitation techniques, and weaponization considerations. Use when actively developing exploits or setting up an exploit dev environment.
offensive-container-escape
Container escape and breakout techniques targeting Docker, containerd, and Podman runtimes. Covers privileged container breakout via host filesystem mount and nsenter, Docker socket abuse through /var/run/docker.sock, Linux capability exploitation including CAPSYSADMIN, CAPSYSPTRACE, and CAPNETADMIN, cgroup v1…