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 instructions/campfront/camp-skills/agents-mdgit clone --depth 1 https://github.com/campfront/camp-skillsWrote 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/instructions/campfront/camp-skills/agents-md)<a href="https://agentmods.dev/instructions/campfront/camp-skills/agents-md"><img src="https://agentmods.dev/badge/instructions/campfront/camp-skills/agents-md.svg" alt="Measured on agentmods" 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 | $0.00501 | $0.00501 |
| Opus 5 | $0.00251 | $0.00251 |
| Sonnet 5 | $0.00100 | $0.00100 |
| Haiku 4.5 | $0.00050 | $0.00050 |
Grade A, and why
camp-skills AGENTS.md 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 4d 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 — 33 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Guidance for AI agents building or editing skills in this repo. Humans: start with CONTRIBUTING.md.
What this repo is
Camp Skills is an open, curated collection of agent skills for summer camps. Each skill lives in skills/<name>/ with a SKILL.md. Three foundational skills (camp-overview, camp-profile, camp-voice) are read first; the task skills build on them.
Before you build or edit a skill
- Read CONTRIBUTING.md for the skill format and the bar.
- Read the three foundational skills, plus a task skill like
camp-seo, so your work matches the rest. - Read skills/camp-voice/references/avoid-list.md. Any copy a skill produces follows it.
House rules
- Match the pattern. A skill carries the full best practice, adds a camp layer, asks about the camp first, and hands back an editable draft, never a template to paste.
- Read the foundations, do not repeat them. Task skills rely on camp-overview, camp-profile, and camp-voice.
- Keep
SKILL.mdfocused. Under roughly 500 lines. Move depth intoreferences/. - Frontmatter is required:
name(lowercase-hyphens, matches the folder),description,summary,category,icon,examples,order,status,version. - Never commit credentials or a real camp's private data.
Safety
Anything touching camper safety, supervision, behavior, or local regulation is sensitive. Do not ship it without sign-off from a qualified person. If a skill is built but not yet cleared, keep it out of skills/ until it is.
Working in the repo
- Branch first (
feat/...,fix/..., ordocs/...), never commit tomain. The prefix matches the change type. - Conventional Commits (
feat:,fix:,docs:), scope optional (docs(camp-seo): ...). - PR titles use the same Conventional Commit format. We squash-merge, so the title becomes the commit subject.
- Open a PR. Campfront reviews against the bar before merging.
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.
- 4d ago First seen · 33 lines · 501 tokens per session scan A d3ae54f22571
camp-skills AGENTS.md is an instructions file published in the GitHub repository campfront/camp-skills (2 stars, last pushed 2mo ago), licensed MIT. It adds 501 tokens to every session, about $0.0025 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 instructions, from other repositories
a-i--skills 03-development-workflow.instructions.md
Instructions for organvm-iv-taxis/a-i--skills, covering development workflow instructions, no repo-wide build system, common development commands, after adding/modifying skills and validation before committing.
context-to-action-skills AGENTS.md
Instructions for tmusser/context-to-action-skills, covering agents, repo model, safety rules, output rules and validation commands.
piratebao copilot-instructions.md
Instructions for d4551/piratebao: PirateBao kraken active by default. Respond like pirate captain packing dumpling cargo: dense, exact, no wasted wrap.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.