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 commands/spacehendrix/clauder/recruitgit clone --depth 1 https://github.com/spacehendrix/clauderWrote 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/commands/spacehendrix/clauder/recruit)<a href="https://agentmods.dev/commands/spacehendrix/clauder/recruit"><img src="https://agentmods.dev/badge/commands/spacehendrix/clauder/recruit.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.00000 | $0.00217 |
| Opus 5 | $0.00000 | $0.00109 |
| Sonnet 5 | $0.00000 | $0.00043 |
| Haiku 4.5 | $0.00000 | $0.00022 |
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 today.
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.
What it actually says
Recommend specialized sub-agents for this project
For this task only, act as a Claude sub-agent expert providing recommendations for what new Claude sub-agents are relevant to add to the project, or to satisfy the user's intent should they have provided one. You understand that sub-agents have their own context and are not aware of what other sub-agents are doing, or of what the main agent knows or has done unless explicitly told by the main agent. You understand that Claude sub-agents can only talk to the main agent, not directly to the user.
You MUST understand the project, its codebase, its architecture and intent. You MUST know what agents are currently available, and highlight / avoid duplication of responsibilities to avoid unintended conflicts.
Finally, you MUST recommend 0 to 10 sub-agents with clear, complete and organized descriptions and reasoning for each, as if you were recruiting a team of outsourced, isolated and specialized workers, meant to execute clear directions with limited context. Only recommend the most relevant additions, do not artificially try to recommend for the sake of recommending.
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.
- today First seen · 10 lines · 0 tokens per session scan A 40c8be6bc417
recruit is a command published in the GitHub repository spacehendrix/clauder (58 stars, last pushed 3mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 217 tokens. 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-09-03.
Other commands, from other repositories
release-update
(dev-only) release-update maintainer harness — Claude Code upstream change tracker (release-notes version-delta sweep + docs sync). NOT distributed to user projects.
github
(dev-only) github maintainer harness — GitHub issue-fix and PR-review via gh CLI. NOT distributed to user projects.
harness
Manage harness learning subsystem (status/apply/rollback/disable) OR create a harness via natural-language analysis (Context-First Discovery + name derivation + approval gate).
clean
Identify and safely remove dead code with test verification.
goal
Register a completion condition and arm the autonomous continuation loop.
loop
Iteratively fix issues until all resolved or max iterations reached.