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/reggiechan74/cc-plugins/draft-emailnpx skills add reggiechan74/cc-plugins --skill draft-emailgit clone --depth 1 https://github.com/reggiechan74/cc-pluginsWhat 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.00100 | $0.01035 |
| Opus 5 | $0.00050 | $0.00517 |
| Sonnet 5 | $0.00020 | $0.00207 |
| Haiku 4.5 | $0.00010 | $0.00103 |
Grade A, and why
Draft Camp Emails 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.
How it starts
The opening of the file, as written. The whole thing — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Draft Camp Emails
Overview
Locate research directory: Read .claude/kids-camp-planner.local.md to get the research_dir path (default: camp-research). All user data paths below are relative to this directory. The family profile is at <research_dir>/family-profile.md.
Draft professional, personalized emails to camp providers. Pull family details from the profile and provider details from research files to create complete, ready-to-send emails. Save drafts to <research_dir>/drafts/ for review before sending.
Email Drafting Workflow
Step 1: Gather Context
Before drafting, read:
- Family profile (
<research_dir>/family-profile.md) for children's details, special needs, contact info - Provider file (
<research_dir>/providers/[provider].md) for camp-specific details, contact email, program names
Step 2: Determine Email Type
Identify the purpose and use the appropriate template structure:
| Email Type | When to Use |
|---|---|
| Inquiry | Asking about program details, availability, pricing |
| Registration | Requesting enrollment or registration information |
| Waitlist follow-up | Following up on waitlist status |
| Special needs / dietary | Informing about allergies, medical needs, accommodations |
| Schedule / logistics | Questions about hours, pickup/dropoff, what to bring |
| Cancellation | Requesting cancellation or date change |
Step 3: Draft the Email
General email guidelines:
- Friendly but professional tone (parent writing to a camp, not a business letter)
- Include child's name, age, and grade
- Reference specific program names and dates
- Be clear about what information or action is needed
- Include relevant medical/dietary info when appropriate
- Keep it concise - camp administrators handle hundreds of emails
Save drafts to: <research_dir>/drafts/[type]-[provider].md
Email Templates
Six templates are available covering all common camp communication scenarios. The inquiry template is shown below as a representative example. For all other templates (registration, waitlist follow-up, special needs/dietary, cancellation, logistics inquiry), see references/email-templates.md.
What ships with it
2 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.
- 2d ago First seen · 121 lines · 100 tokens per session scan A ffb722dcf059
Draft Camp Emails is a skill published in the GitHub repository reggiechan74/cc-plugins (6 stars, last pushed 3mo ago), licensed MIT. It adds 100 tokens to every session and 1,035 once invoked, about $0.0005 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.