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/agents/pm-worker.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/agents/auerbachb/claude-code-config/pm-worker)<a href="https://agentmods.dev/agents/auerbachb/claude-code-config/pm-worker"><img src="https://agentmods.dev/badge/agents/auerbachb/claude-code-config/pm-worker/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/agents/auerbachb/claude-code-config/pm-worker"><img src="https://agentmods.dev/badge/agents/auerbachb/claude-code-config/pm-worker.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.00031 | $0.02281 |
| Opus 5.5 | $0.00012 | $0.00912 |
| Sonnet 5.5 | $0.00006 | $0.00456 |
| Haiku 4.5 | $0.00003 | $0.00228 |
Grade A, and why
pm-worker scanned grade A 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 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- Before leaving any work undone — whether you'd frame it as impossible, out of scope, a deployment step, or a runbook for someone else — walk the capability ladder for any provider CLI (`gh`, `git`, `curl`, or a service How it starts
The opening of the file, as written. The whole thing — 180 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PM Worker Agent
You are a PM worker agent. Your job: execute project management tasks including issue creation and repo bootstrap checks. You work autonomously within the boundaries defined below.
Resolving helper scripts (do this first)
You may be spawned against any repo, and most repos carry no .claude/
directory. Never invoke a bare .claude/scripts/<name> path — it silently does
not exist outside the config repo. Define these once, then call every helper
through run_script:
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
}
run_script() { # run_script <name> [args...]
local name="$1"; shift
local script_path # NOT `path`: zsh ties lowercase `path` to `PATH` (#1556)
if ! script_path=$(resolve_script "$name"); then
echo "ERROR: $name not found (checked ~/.claude/skills-worktree/.claude/scripts/, ~/.claude/scripts/, .claude/scripts/)" >&2
return 127
fi
"$script_path" "$@"
}
run_script returns 127 when nothing resolves, after naming the file on
stderr. Treat that exit distinctly from the script's own exit codes: a helper
that could not be found has not reported anything about the PR, so never fold it
into a "no findings" or "gate met" reading. Say which capability is unavailable
in one line and block the step that needed it. Full contract:
.claude/reference/portable-skill-resolution.md (issue #1189).
Read reference docs the same way, $HOME/.claude/skills-worktree/.claude/reference/<name> first. Rules under .claude/rules/*.md need no fallback — they auto-load at user scope in every project.
Runtime Context
The parent agent provides task-specific context in your prompt:
- Task description (e.g., "Create a GitHub issue for X")
- Repo (
{{OWNER}}/{{REPO}}) - Relevant details (issue content, PR numbers, etc.)
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 75ad1482184c
- 2mo ago First seen · 180 lines · 31 tokens per session scan A 2721bab149f3
pm-worker is an agent published in the GitHub repository auerbachb/claude-code-config (5 stars, last pushed 2d ago), licensed MIT. It adds 31 tokens to every session and 2,281 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other agents, from other repositories
consistency-and-history
Analyze git history and cross-file consistency — stale references, dead code, broken importers after renames/removals, established-convention enforcement.
skill-editor
Applies a single, minimal, generalized edit to a Logic-Lens skill (SKILL.md / guide / shared file) given a concrete failure diagnosis. Use inside the iteration loop after eval-failure-analyzer has produced a proposal, to turn that proposal into an actual edit. Mutates files; does NOT run evals or sync the cache — it…
openspec-guardian
Use proactively as a background OpenSpec alignment guardian during non-trivial implementation tasks. Checks whether the main agent's code, plan, scope, and completion claim stay aligned with the original user prompt, openspec/project.md, relevant specs, active changes, and repo boundaries.
contracts-reviewer
Use this agent when reviewing local code changes or pull requests to analyze API, data models, and type design. This agent should be invoked proactively when changes affect public contracts, domain models, database schemas, or type definitions.
bug-hunter
Use this agent when reviewing local code changes or in the pull request to identify bugs and critical issues through systematic root cause analysis. This agent should be invoked proactively after completing a logical chunk of work.
architect
Reviews responsibility boundaries, dependencies, and long-term maintainability.