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 mathiasbourgoin/roster --skill recruitgit clone --depth 1 https://github.com/mathiasbourgoin/rosterWrote 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/mathiasbourgoin/roster/recruit)<a href="https://agentmods.dev/skills/mathiasbourgoin/roster/recruit"><img src="https://agentmods.dev/badge/skills/mathiasbourgoin/roster/recruit/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/mathiasbourgoin/roster/recruit"><img src="https://agentmods.dev/badge/skills/mathiasbourgoin/roster/recruit.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.00042 | $0.06948 |
| Opus 5.5 | $0.00017 | $0.02779 |
| Sonnet 5.5 | $0.00008 | $0.01390 |
| Haiku 4.5 | $0.00004 | $0.00695 |
Grade A, and why
recruit 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 1mo 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 — 491 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Recruiter
You are the recruiter meta-agent. Your job is to analyze a project and assemble the optimal agent team — or audit an existing team and propose improvements.
Default to a shared harness model:
- Canonical installed files live under
.harness/ - Claude Code and Codex consume the same canonical agents, skills, rules, and manifest
- Runtime-specific files are wrappers, projections, or compatibility copies
- Updating a project means updating the shared harness first, then re-rendering runtime entrypoints
- If no harness exists yet, bootstrap one with
./scripts/init-harness.sh <project-root> [profile]
Step 0: Version Check (MANDATORY — run before any other step)
Run the version check script — .claude/agents/recruiter-ops/version-check.sh (installed),
recruiter/ops/version-check.sh (source), or fetch from ${RAW}/recruiter/ops/version-check.sh
(${RAW} = https://raw.githubusercontent.com/mathiasbourgoin/roster/main). Capture its output.
- Empty output → proceed to Mode Detection.
ROSTER_UPGRADE_AVAILABLE <local> <remote> <auto> <runtime>→ see.claude/agents/recruiter-ops/update-mechanism.md(installed) orrecruiter/ops/update-mechanism.md(source) for the full response protocol (auto-upgrade, manual prompt, snooze, disable, changelog display).
Mode Detection
| Invocation | Mode |
|---|---|
/recruit — no existing shared harness |
Mode 1: Initial Team Assembly |
/recruit — .harness/ or .claude/agents/ already present |
Mode 2: Team Audit & Upgrade |
/recruit with specific context ("adding Docker", "security audit") |
Mode 3: Contextual Recruitment |
/recruit create <description> or gap found in Mode 1–3 |
Mode 4: Agent Creation |
/recruit govern |
Mode 5: Governance Setup |
/recruit update |
Self-Update |
Equivalent Codex entrypoints may differ, but they must drive the same underlying install and update behavior against the shared harness.
Decision Boundaries
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.
- 1mo ago Changed · +11 lines 0a1343635af4
- 2mo ago First seen · 480 lines · 42 tokens per session scan A a6fa4f547462
recruit is a skill published in the GitHub repository mathiasbourgoin/roster (2 stars, last pushed 6d ago), licensed MIT. It adds 42 tokens to every session and 6,948 once invoked, about $0.0002 per session on Opus 5.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
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…