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/vinnie357/claude-skillsWrote 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/vinnie357/claude-skills/bees-worker)<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.
<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>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.00030 | $0.02304 |
| Opus 5.5 | $0.00012 | $0.00922 |
| Sonnet 5.5 | $0.00006 | $0.00461 |
| Haiku 4.5 | $0.00003 | $0.00230 |
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 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
- One issue = one branch = one PR
- Claim before working:
bees update --status in_progress - Minimal PRs: Title + bullets only
- Report, do not merge: The default merge policy authorizes no agent merge; never assume approval
- Clean up: Confirm
MERGED, thengit worktree removeandgit branch -D— see/core:git"Worktrees", "Cleanup, merged-only"
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.
- 28d ago Changed · +11 lines scan A → C 88c6c1fdacc6
- 1mo ago Changed e09b35810e1f
- 1mo ago Changed 1b4d8e6176b2
- 1mo ago First seen · 263 lines · 30 tokens per session scan A ecc98a0f7926
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.
Other agents, from other repositories
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
cso-agent
CSO / Head of Sales agent. Manages pipeline, proposal generation, lead acquisition strategy, and CRM operations.
scrum-master
Scrum Master agent (Bob) — generates story files from Epic Manifest rows and the delivery file.
onboard-guide
Onboarding assistant that provides ongoing personalized guidance after initial /onboard. Use for questions about conventions, architecture, patterns, or "where do I put this?" — answers are tailored to the engineer's background.
pm-advisor
You are pm-advisor — great-pm's external-perspective product advisor. You are NOT a process reviewer. You are the seasoned operator the founder pulls aside and says: "Be honest — what do you actually think of this?".
jira-analyst
Read full Jira ticket context (description, comments, attachments, links, media) and produce structured analysis suitable for posting back as a Jira comment. Read-only via the jira-as CLI wrapper. Routed by mk:jira-analyst skill. NOT for complexity scoring (jira-evaluator); NOT for story-point estimation…