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/campfront/camp-skills/evening-programnpx skills add campfront/camp-skills --skill evening-programgit clone --depth 1 https://github.com/campfront/camp-skillsWhat 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.00106 | $0.02040 |
| Opus 5 | $0.00053 | $0.01020 |
| Sonnet 5 | $0.00021 | $0.00408 |
| Haiku 4.5 | $0.00011 | $0.00204 |
Grade A, and why
evening-program 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 — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
evening-program
Plan campfires and all-camp evening programs that kids remember and that wind down for bed. This carries evening-program best practice with the camp's safety and sleep guardrails on top.
It is written for you, the agent. Use camp-profile for the camp's ages and facilities, and camp-overview for where the session sits. The thing to get right is the energy arc landing calm, because campers go straight to bed, and the safety around fire and the dark. For the games inside the program, draw on activity-planner. Treat what you produce as a starting point, and keep what the camp already loves.
Ask first
Start from what is known, then ask only for the gaps.
1. Read the camp's context first. If a camp profile exists (.agents/camp-profile.md), read it for ages, facilities, and traditions, and ask only for what is missing.
2. Ask only the task-specific gaps:
- Ages and the number of campers.
- Indoor or outdoor, and whether a real campfire is possible (a fire ban, a fire ring).
- The time and length, and how much runway there is to wind down before lights-out.
- The energy needed (burn off a high day, or settle an over-stimulated one).
- The occasion: first night, a mid-session theme night, or the last night, which changes how the whole program should feel.
- The facilities and kit (fire ring, stage, hall, sound, flashlights), and the rain backup.
- The traditions the camp already runs, the staff available and how willing they are to perform, and any campers prone to homesickness or fear.
3. How far to go (the depth dial). Match it to the director's goal and how much they want to take on. Default to one program for tonight, and offer to go deeper.
- Quick wins (low effort): one evening program for tonight, fit to the occasion, the energy, and the ages.
- Solid setup (medium effort): a set for the session (a campfire, a wide game, a theme night) with the wind-down for each.
- Full build (high effort): the session's evening calendar arced across the days, with rain plans and the camp's traditions worked in.
What ships with it
1 file 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 · 118 lines · 106 tokens per session scan A bd7946b1c49f
evening-program is a skill published in the GitHub repository campfront/camp-skills (2 stars, last pushed 2mo ago), licensed MIT. It adds 106 tokens to every session and 2,040 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
happiness-skill
当用户问「怎么才能更幸福/为什么得到了还不满足/怎么减少焦虑」时调用。 核心理念: 幸福是缺憾感清空的默认状态, 是可训练的技能; 欲望是与自己的契约(得到前不快乐), 同时只留一个重大欲望; 活在当下。 不适用于: 临床抑郁等需要专业治疗的场景(本书方法不能替代医疗)。 Triggers: 幸福/不快乐/欲望/焦虑/知足/活在当下/happiness/desire/anxiety.
ddia-systems
Design data systems by understanding storage engines, replication, partitioning, transactions, and consistency models. Use when the user mentions "database choice", "which database should I use", "SQL or NoSQL", "replication lag", "partitioning strategy", "consistency vs availability", "stream processing", "ACID…
improve-website
Guided journey from a live website that underperforms to a prioritized, evidence-backed backlog of conversion, usability, message, and speed fixes - each shipped as a testable experiment. Orchestrates eight skills phase by phase - cro-methodology, ux-heuristics, refactoring-ui, web-typography, storybrand-messaging…
ios-hig-design
Design native iOS interfaces following Apple Human Interface Guidelines. Use when the user mentions "iPhone app", "iPad layout", "SwiftUI", "UIKit", "Dynamic Island", "safe areas", "HIG compliance", "SF Symbols", "haptic feedback", "iOS accessibility", "make my app feel native", or "follow Apple design guidelines".…
jobs-to-be-done
Discover what customers truly need by analyzing the "job" they hire your product to do. Use when the user mentions "customer discovery", "why customers churn", "what job does this solve", "competing against luck", "product-market fit", "switching behavior", "milkshake moment", or "functional vs emotional jobs". Also…
lean-startup
Design MVPs, validated learning experiments, and pivot-or-persevere decisions using Build-Measure-Learn. Use when the user mentions "MVP scope", "validated learning", "pivot or persevere", "vanity metrics", "test assumptions", "innovation accounting", "build-measure-learn", "minimum viable experiment", "should we…