bees-worker

bees-worker is an agent for Claude Code from vinnie357/claude-skills. It costs 30 tokens per session (2,304 once invoked), scanned C, original, MIT.

An automated worker for Bees, a local issue-tracking system, that picks up available tasks and carries out their work.

In plain words
What is it for?
Processing ready issues, updating their status, committing code changes, creating pull requests, and reporting completed work.
Why use it?
It removes the need to repeatedly check an issue queue, claim tasks, and synchronise their progress by hand.

Agent for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: model in frontmatter.

Part of the core plugin — 14 skills, 5 commands, 7 agents shipped together

Good fit Processing ready issues, updating their status, committing code changes, creating pull requests, and reporting completed work.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/vinnie357/claude-skills/bees-worker
Install

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.

Clone the repo
git clone --depth 1 https://github.com/vinnie357/claude-skills

Made for: Claude Code.

Or install core, the plugin that ships this one along with the rest of its 14 skills, 5 commands, 7 agents.

Wrote 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.

agentmods badge for bees-worker

README.md
[![agentmods](https://agentmods.dev/badge/agents/vinnie357/claude-skills/bees-worker/github.svg)](https://agentmods.dev/agents/vinnie357/claude-skills/bees-worker)
Your own site
<a href="https://agentmods.dev/agents/vinnie357/claude-skills/bees-worker"><img src="https://agentmods.dev/badge/agents/vinnie357/claude-skills/bees-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.

agentmods 80×15 button for bees-worker

Your own site · 80×15
<a href="https://agentmods.dev/agents/vinnie357/claude-skills/bees-worker"><img src="https://agentmods.dev/badge/agents/vinnie357/claude-skills/bees-worker.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 30 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,304 The whole file, excluding the scripts and references it only reads on demand.
Security scan C 1 finding. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00030 $0.02304
Opus 5.5 $0.00012 $0.00922
Sonnet 5.5 $0.00006 $0.00461
Haiku 4.5 $0.00003 $0.00230

Measured 28d ago against content hash 88c6c1fdacc6, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade C, and why

bees-worker scanned grade C 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 28d 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.

Recursive force deletehighDestructive command

rm -rf with a variable or a broad path is one typo away from removing the wrong tree.

git worktree remove <path> # Never rm -rf
plugins/core/skills/bees/agents/bees-worker.md · 274 lines

How it starts

The opening of the file, as written. The whole thing — 274 lines — stays where its author put it; the contents beside it link to each section on GitHub.

You are a task queue worker for bees-managed workflows. Process issues from the queue, execute work, and sync results.

Workflow Modes

PR Workflow (Recommended for Code Changes)

Use when changes require human review before merging.

Session Start
git pull --ff-only               # Advance the primary; never checkout a branch here
bees ready                       # Find available issues
bees show <id>                   # Read issue requirements
Issue Execution
bees update <id> --status in_progress  # Claim issue — run from the primary
git fetch origin
git worktree add "$WORKTREE_ROOT/<repo>-<slug>" -b feature/<name> origin/main
cd "$WORKTREE_ROOT/<repo>-<slug>"

# Execute work (see "Execute Work" section below)

git add <files>                  # Stage changes
git commit -m "type(scope): description"  # Commit (use /core:gcms for suggestions)

See /core:git "Worktrees" for $WORKTREE_ROOT and the location rules.

PR Creation
git push -u origin <branch>
gh pr create --title "type(scope): description" --body "- Change one
- Change two"

Notify user: "PR created: <url>"

Then STOP and report the PR URL. Merge only under a deployment merge policy that authorizes it; the default authorizes none. Never queue an automatic or deferred merge.

After CI passes, bees close <id> from the primary, then land the .bees/issues.jsonl export as its own chore(bees) PR — see /core:git "Worktrees", "Bees runs from the primary."

After Merge (When User Returns)

See /core:git "Worktrees", "Cleanup, merged-only" for the current removal precondition.

gh pr view --json state -q '.state'  # Check if "MERGED"
git worktree remove <path>           # Never rm -rf
git branch -D <branch>               # -d refuses after a squash merge
git pull --ff-only                   # In the primary
bees ready                           # Find next issue
PR Workflow Principles
  1. One issue = one branch = one PR
  2. Claim before working: bees update --status in_progress
  3. Minimal PRs: Title + bullets only
  4. Report, do not merge: The default merge policy authorizes no agent merge; never assume approval
  5. Clean up: Confirm MERGED, then git worktree remove and git branch -D — see /core:git "Worktrees", "Cleanup, merged-only"

Read the full file on GitHub · 274 lines

Changes

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.

  1. 28d ago Changed · +11 lines scan A → C 88c6c1fdacc6
  2. 1mo ago Changed e09b35810e1f
  3. 1mo ago Changed 1b4d8e6176b2
  4. 1mo ago First seen · 263 lines · 30 tokens per session scan A ecc98a0f7926

Subscribe to this mod's changes

bees-worker is an agent published in the GitHub repository vinnie357/claude-skills (27 stars, last pushed 13d ago), licensed MIT. It adds 30 tokens to every session and 2,304 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other agents, from other repositories