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 agentmods add skills/bguivarch/skillforge/client-emailnpx skills add bguivarch/skillforge --skill client-emailgit clone --depth 1 https://github.com/bguivarch/skillforgeWhat 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 | $0.00008 | $0.00334 |
| Opus 5 | $0.00004 | $0.00167 |
| Sonnet 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 2d 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.
- 2d 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 7mo ago), licensed Apache-2.0. It adds 8 tokens to every session and 334 once invoked, about $0.0000 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
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-tls-attacks
Comprehensive methodology for auditing and exploiting TLS/SSL implementations and misconfigurations across network services and mobile applications. Covers protocol downgrade attacks including POODLE (CVE-2014-3566) against SSLv3 CBC padding, DROWN (CVE-2016-0800) cross-protocol attack leveraging SSLv2 export ciphers…
offensive-advanced-redteam
Comprehensive red team operations methodology covering full engagement lifecycle from planning through reporting. Addresses engagement scoping and rules of engagement negotiation, multi-tier C2 infrastructure design with redirectors and domain fronting, malleable traffic profiles and beacon tradecraft, OPSEC…
offensive-social-engineering
Social engineering attack techniques beyond email phishing for authorized red team and physical penetration testing engagements. Covers pretexting methodology (persona creation, authority and urgency psychological triggers, rapport building), vishing (voice phishing via caller ID spoofing, IVR system exploitation…