Borrowing it
Nothing to install: this file belongs to auerbachb/claude-code-config. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/auerbachb/claude-code-config/main/.claude/skills/subagent/SKILL.mdgit clone --depth 1 https://github.com/auerbachb/claude-code-configWrote 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/auerbachb/claude-code-config/subagent)<a href="https://agentmods.dev/skills/auerbachb/claude-code-config/subagent"><img src="https://agentmods.dev/badge/skills/auerbachb/claude-code-config/subagent/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/auerbachb/claude-code-config/subagent"><img src="https://agentmods.dev/badge/skills/auerbachb/claude-code-config/subagent.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.00062 | $0.36009 |
| Opus 5.5 | $0.00025 | $0.14404 |
| Sonnet 5.5 | $0.00012 | $0.07202 |
| Haiku 4.5 | $0.00006 | $0.03601 |
Grade B, and why
subagent scanned grade B with 1 finding 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 29d 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
Then verify: `--get` shows `phase_completed: "B"` with your SHA, and `find ~/.claude/handoffs -name 'pr-{PR_NUMBER}-handoff.json'` returns exactly ONE path — the `{owner}/{repo}` one. A second match means a call lost its How it starts
The opening of the file, as written. The whole thing — 1,777 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Execute one or more issues as subagents within the current thread. Each issue goes through the full Phase A/B/C orchestration protocol (fix, review, merge prep) while this skill monitors progress and manages transitions. Inline execution is the default for issues of any tier. Only two of Step 4's three too-big criteria route an issue out to a separate thread; the third — "should be split into multiple PRs" — is decomposed into an inline increment chain instead (Step 5.1).
Parse $ARGUMENTS as space-separated issue references. Strip # prefixes to get bare issue numbers. If no arguments provided, ask the user which issue(s) to execute.
Step 0: Resolve shared tooling
/subagent is symlinked into every repo, but its helper scripts and reference docs are not — most repos carry no .claude/ directory. Resolve them; never invoke a bare .claude/scripts/… path. Full contract and the classified dependency inventory: .claude/reference/portable-skill-resolution.md (issue #1189).
resolve_script() {
local name="$1" candidate
for candidate in \
"$HOME/.claude/skills-worktree/.claude/scripts/$name" \
"$HOME/.claude/scripts/$name" \
".claude/scripts/$name"; do
if [[ -x "$candidate" ]]; then echo "$candidate"; return 0; fi
done
return 1
}
ISSUE_CLAIM=$(resolve_script issue-claim.sh || true)
CR_PLAN=$(resolve_script cr-plan.sh || true)
SESSION_STATE_SH=$(resolve_script session-state.sh || true)
ISSUE_DEDUP=$(resolve_script issue-dedup.sh || true)
ESTIMATE_RESOLVE_SH=$(resolve_script estimate-resolve.sh || true)
SPLIT_THRESHOLDS_SH=$(resolve_script split-thresholds.sh || true)
OVERRUN_CHECK_SH=$(resolve_script overrun-check.sh || true)
TABLE_FRESHNESS_SH=$(resolve_script table-freshness.sh || true)
USAGE_HORIZON_SH=$(resolve_script usage-horizon.sh || true)
ACTIVE_WORK_CAP_SH=$(resolve_script active-work-cap.sh || true)
handoff-state.sh (Step 8), ac-checkboxes.sh, escalate-review.sh, and local-review.sh are resolved by the phase agents themselves, inside the spawn prompts — the RESOLVE block inserted with SAFETY/MINDSET/SKILLS carries the same candidate order to them. Read reference docs (chip-launching.md, subagent-phase-guardrails.md, issue-claim.md, merge-sequencing.md) through the matching .claude/reference/ order.
When something does not resolve, say so in one line; never skip the contract silently.
subagent-phase-guardrails.mdunreadable → required. PrintERROR: subagent-phase-guardrails.md not found (checked all three paths) — SAFETY/MINDSET/SKILLS/RESOLVE blocks unavailableand spawn nothing. Those blocks are the safety restatement every spawn carries; a phase agent launched without them is not a degraded spawn, it is an unsafe one.chip-launching.mdunreadable → required for Step 5's route-to-thread branch only. PrintERROR: chip-launching.md not found (checked all three paths) — too-big routing gate unavailable, and queue the issue inline rather than routing it out: inline is the default the gate exists to protect (#1189), so failing toward it is correct.SESSION_STATE_SHempty → required. PrintERROR: session-state.sh not found (checked all three paths) — agent tracking and refill state unavailableand do not spawn; an untracked agent is one nothing will ever reap.ISSUE_CLAIMempty → optional. PrintDEGRADED: issue-claim.sh not found (checked all three paths) — Step 6 claim gate skippedand continue.CR_PLANempty → optional. PrintDEGRADED: cr-plan.sh not found (checked all three paths) — CR plan detection skippedand continue with Claude's own plan.ESTIMATE_RESOLVE_SHempty → optional. PrintDEGRADED: estimate-resolve.sh not found (checked all three paths) — planning-bound lookup unavailable; overrun check skippedand skip the overrun check in Step 8 (BOUND_MIN cannot be derived without it).OVERRUN_CHECK_SHempty → optional. PrintDEGRADED: overrun-check.sh not found (checked all three paths) — in-flight overrun alerts unavailableand skip the overrun check in Step 8.SPLIT_THRESHOLDS_SHempty → optional. PrintDEGRADED: split-thresholds.sh not found (checked all three paths) — using default thresholds 180/120and continue with those documented defaults. The time trigger still fires (Step 4 criterion 3); it just cannot see a repo that retuned the knobs. Silently skipping the trigger instead would be worse — it would turn a missing config reader into a missing sizing check.USAGE_HORIZON_SHempty → optional. PrintDEGRADED: usage-horizon.sh not found (checked all three paths) — pre-emptive usage-horizon park unavailable; the reactive park still appliesand continue. Step 8's gate then holdsunknownon every cycle, which starts nothing new and parks nothing — the conservative direction, and the same posture a displaced session already reads.ACTIVE_WORK_CAP_SHempty → optional. PrintDEGRADED: active-work-cap.sh not found (checked all three paths) — per-repo PIPELINE_CEILING unavailable, using the default ceiling of 4and run Step 7 withCEILING=4and no cap term. A non-zero exit from--ceilingor--capon a script that did resolve (they exit non-zero only on a usage error — a bad config value warns and prints the default instead) is not a default: Step 7 setsLIMIT=0and launches nothing new rather than sizing against a guessed number.TABLE_FRESHNESS_SHempty → optional. PrintDEGRADED: table-freshness.sh not found (checked all three paths) — hourly table-freshness floor unavailable; re-render the "Running now" table on every heartbeat insteadand continue. Failing toward more table renders is correct: the floor exists to guarantee a table at least hourly, so its absence must never buy the thread permission to emit fewer.
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.
- 29d ago Changed · +17 lines dcbfb973ee49
- 1mo ago Changed · +224 lines 5364414582d7
- 1mo ago Changed 5ba3ebe4cc7d
- 1mo ago Changed · +122 lines f3bbf00242b2
- 1mo ago Changed · +220 lines d1d29792e418
- 1mo ago Changed · +19 lines 0459516f06fc
- 1mo ago Changed · +378 lines a79cacb5aa85
- 2mo ago First seen · 797 lines · 62 tokens per session scan B 806bd8e20b01
subagent is a skill published in the GitHub repository auerbachb/claude-code-config (5 stars, last pushed 2d ago), licensed MIT. It adds 62 tokens to every session and 36,009 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
skeptic
Adversarial reviewer for Bug Hunter. Challenges each behavioral finding against actual code, checks defenses, and preserves unresolved cases for independent review.
referee
Final arbiter for Bug Hunter. Independently verifies behavioral findings, resolves Skeptic challenges, and calibrates severity and confidence.
commit-security-scan
Scan code changes for security vulnerabilities using Bug Hunter-native artifacts and STRIDE context. Use whenever the user asks for PR security review, commit-diff scanning, staged-change security checks, branch-comparison security review, or pre-merge security analysis of changed code.
robin
Use whenever an agent creates, updates, reviews, or completes a GitHub pull request. Detect whether Robin is installed in the repository; when it is, automatically drive the PR through a bounded review, verified-fix, reply, thread-resolution, re-review, authorized-merge, and cleanup loop without requiring the user to…
adr
Create and manage Architecture Decision Records. Documents significant technical decisions with context, alternatives, and consequences. Also supports evaluate (assess proposals) and design (system design) modes.
deploy-checklist
Pre-deployment verification checklist. Generates customized checklists based on tech-stack with rollback triggers. Auto-invoked by /draft:upload.