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 skills add campfront/camp-skills --skill staff-job-postgit 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/skills/campfront/camp-skills/staff-job-post)<a href="https://agentmods.dev/skills/campfront/camp-skills/staff-job-post"><img src="https://agentmods.dev/badge/skills/campfront/camp-skills/staff-job-post/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/campfront/camp-skills/staff-job-post"><img src="https://agentmods.dev/badge/skills/campfront/camp-skills/staff-job-post.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00109 | $0.01973 |
| Opus 5 | $0.00055 | $0.00986 |
| Sonnet 5 | $0.00022 | $0.00395 |
| Haiku 4.5 | $0.00011 | $0.00197 |
Grade A, and why
staff-job-post 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 11d 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 — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.
staff-job-post
Write counselor and specialist job posts that bring in the right seasonal staff and screen out the wrong ones. This carries job-description craft with a camp layer on top: the real screening, certifications, and training a camp role requires, and how to sell a hard summer job to a young or international applicant.
It is written for you, the agent. Use camp-voice for the writing, camp-profile for the camp's facts and voice, and camp-overview for how camps are staffed and the J-1 route for international staff. State the real requirements honestly, because the screening is required for child safety and by law, and never write an ad that discriminates.
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.mdor.claude/camp-profile.md), read it for the camp's facts and voice. Do not re-ask what it answers. - Use camp-voice for the writing and its avoid-list, and camp-overview for the staffing structure and J-1.
- If no profile exists, offer to capture one with the camp-profile skill, then continue.
2. Ask only the task-specific gaps:
- The role: title, who it reports to, the ages it works with, and what it owns day to day.
- The one thing this person has to be great at.
- The real requirements: minimum age, required certifications, and the camp's screening and training.
- Pay and the practical terms: dates, room and board, time off, transport, and whether the role is open to international (J-1) applicants.
- Where the post will run.
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 strong post, and offer to go deeper.
- Quick wins (low effort): one strong post for one role, with the real requirements and a clear way to apply.
- Solid setup (medium effort): posts for the core roles (counselor, a specialist, a senior role), plus the screening, certification, and equal-opportunity wording the camp can reuse.
- Full build (high effort): the season's roles, a distribution plan, and a reusable template set.
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.
- 11d ago First seen · 115 lines · 109 tokens per session scan A bfe28cf130bd
staff-job-post is a skill published in the GitHub repository campfront/camp-skills (2 stars, last pushed 2mo ago), licensed MIT. It adds 109 tokens to every session and 1,973 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
run-behavioral-interview
Use when conducting a job interview — to ask structured behavioral questions using the STAR method so that candidate evaluation is based on demonstrated past behavior rather than self-reported traits or hypothetical answers.
run-reference-check
Use when evaluating a finalist candidate for a role — to conduct structured phone reference calls that surface specific performance evidence, development needs, and potential red flags that interviews cannot reveal.
write-role-scorecard
Use when defining a role before hiring for it — to specify the outcomes the new person must achieve, the competencies required to achieve them, and the cultural requirements, so that interview questions target evidence of actual job performance rather than proxies like credentials or experience.
apply-merit-selection
Use when making any talent selection, promotion, or recommendation decision — to test your evaluation against the reversed-relationship check, because evaluator relationship bias systematically corrupts talent decisions even in well-intentioned evaluators, and merit discipline must be applied at the moment of…
apply-peter-principle-check
Use when designing a promotion process or deciding whether to promote someone based on strong current-role performance — explicitly test whether the skills that made them successful there are the same skills the next level requires, because promotion systems that reward current-role performance alone systematically…
write-job-description
Use when creating or improving a job posting, role description, or position specification to attract qualified candidates.