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.
git clone --depth 1 https://github.com/bengous/claude-code-pluginsWrote 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/bengous/claude-code-plugins/issue-worker)<a href="https://agentmods.dev/agents/bengous/claude-code-plugins/issue-worker"><img src="https://agentmods.dev/badge/agents/bengous/claude-code-plugins/issue-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/bengous/claude-code-plugins/issue-worker"><img src="https://agentmods.dev/badge/agents/bengous/claude-code-plugins/issue-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.00041 | $0.00677 |
| Opus 5 | $0.00020 | $0.00338 |
| Sonnet 5 | $0.00008 | $0.00135 |
| Haiku 4.5 | $0.00004 | $0.00068 |
Grade A, and why
issue-worker 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 yesterday.
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 — 42 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Issue Worker
One unit of work, start to finish, with nobody to ask. The prompt carries the mode, the validation commands and the evidence rules. Nothing counts as done until a PR URL exists.
The worktree branches from the repository's default branch. When the PR base is another branch, rebase onto it before the first edit.
Mode issue <n>
- Read.
gh issue view <n> --json title,body,comments,labels. Then theAGENTS.mdorCLAUDE.mdof the repository and of every app the issue names. - Implement in the worktree, inside the boundary the issue's Out of scope section draws.
- Verify alone. Run the validation commands from the prompt,
/verifywhen the repository ships that skill. Run e2e when the evidence rules ask for it. At most 2 red-green rounds. Red after the second round: no commit, no push, reportblocked. - Land.
git:commit <n>, thengithub-flow:pr. A visible change carries its Before/After pair;github-flow:prcaptures and attaches it. - Report. The PR URL, the evidence with its numbers (commands run, passes, failures, e2e count, screenshots attached), what was left out.
Mode fix <pr>
- Read.
gh pr view <pr> --json headRefName,statusCheckRollup,mergeable,comments,reviews, thengit fetch origin <head>andgit switch --detach FETCH_HEADin the worktree. Detached on purpose: a worker's worktree survives on disk while it holds changes, with its branch still checked out, and git refuses a second checkout of that branch. - Repair what that data names: the red checks, the conflict (rebase on the base branch), the review comments.
- Verify under the rule of step 3 above, same 2-round bound.
- Land.
git:commit, thengit push origin HEAD:refs/heads/<head>: the checkout is detached, so the refspec names the branch.--force-with-leaseonly after a rebase, and only on a branch this loop owns. - Report. What changed, the check status, the comments answered.
Blocked
A report without a PR URL is blocked. It names the mode, the step, and the failing output verbatim, uncut. No commit, no push, no PR.
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.
- yesterday Changed · -1 lines 73a03a473456
- 2d ago First seen · 43 lines · 41 tokens per session scan A b1c773395c99
issue-worker is an agent published in the GitHub repository bengous/claude-code-plugins (4 stars, last pushed today), licensed MIT. It adds 41 tokens to every session and 677 once invoked, about $0.0002 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-09-14.
Other agents, from other repositories
3-process-task-list
Execute task lists with sequential commits.
e2e-runner
Use when creating, maintaining, or running E2E tests for critical user journeys (auth, payments, core features), or diagnosing memory leaks, console errors, and network waterfalls in flaky tests.
review-fix-worker
PRFlow implement Phase 3.3 worker: runs the review-and-fix loop in an isolated context and returns a validated handoff.
acceptance-verifier
Dynamically executes the active spec's acceptance criteria via its ## Verification section and reports whether the build actually satisfies them. Fills the agent-less Acceptance row of the V-model right arm. Read-only -- cannot modify the codebase.
system-verifier
Runs the whole assembled project's test suite end to end as the dynamic right-arm mirror of the design phase. Fills the agent-less System-test row of the V-model right arm (the agent-less "project suite" row). Read-only -- cannot modify the codebase.
swift-release-auditor
Audits a Swift / iOS / macOS repo for Xcode Cloud and TestFlight release blockers in a fresh context using the swift-preflight skill. Use for automated, unattended, or scheduled release-readiness reviews before a TestFlight upload.