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/setupnpx skills add reggiechan74/cc-plugins --skill setupgit 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.00080 | $0.02251 |
| Opus 5 | $0.00040 | $0.01125 |
| Sonnet 5 | $0.00016 | $0.00450 |
| Haiku 4.5 | $0.00008 | $0.00225 |
Grade A, and why
Camp Planner Setup 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 — 177 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Camp Planner Setup
Overview
Initialize the kids-camp-planner workspace by creating the research folder structure, seeding it with templates and examples, collecting the family profile, and configuring API keys. This is typically the first step before any camp planning activity.
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.
Setup Workflow
Step 0: Choose Research Directory Name
Ask the user what they'd like to name their research directory using AskUserQuestion:
- Default:
camp-research(recommended) - The user may choose a custom name (e.g.,
camps,camp-planning,kids-camps) - This directory will hold all camp research data: providers, schedules, budgets, drafts, etc.
Store the chosen name — it will be written to .claude/kids-camp-planner.local.md as research_dir in Step 3.
Step 1: Create Research Folder Structure and Seed Files
Create the following directory structure in the user's current working directory, using the research directory name chosen in Step 0:
<research_dir>/
├── family-profile.md # Full family profile (seeded from plugin, filled in Step 2)
├── providers/ # Individual camp provider files
├── templates/
│ └── provider-template.md # Provider file template for reference
├── examples/
│ ├── ymca-cedar-glen.md # YMCA Cedar Glen example
│ └── boulderz-etobicoke.md # Boulderz Climbing example
├── drafts/ # Draft emails
├── school-calendars/ # Saved school calendar data for this family
├── summer-YYYY/ # Summer period planning
├── march-break-YYYY/ # March break planning
├── fall-break-YYYY/ # Fall break planning (private schools)
└── pa-days-YYYY-YYYY/ # PA day coverage
Seed files from plugin: Copy the following files from the plugin into the research directory so the user has templates and examples visible in their project:
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 · 177 lines · 80 tokens per session scan A 1364ac6348f7
Camp Planner Setup is a skill published in the GitHub repository reggiechan74/cc-plugins (6 stars, last pushed 3mo ago), licensed MIT. It adds 80 tokens to every session and 2,251 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…