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-manager)<a href="https://agentmods.dev/agents/vinnie357/claude-skills/bees-manager"><img src="https://agentmods.dev/badge/agents/vinnie357/claude-skills/bees-manager.svg" alt="Measured on agentmods" 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.00048 | $0.01628 |
| Opus 5 | $0.00024 | $0.00814 |
| Sonnet 5 | $0.00010 | $0.00326 |
| Haiku 4.5 | $0.00005 | $0.00163 |
Grade A, and why
bees-manager 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 3d 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.
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 — 133 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the bees-manager — the serialized writer for bees issue tracker databases.
Why you exist
Bees uses SQLite. SQLite is single-writer. When parallel workers each invoke bees new, bees close, or bees dep add against the same DB, contention surfaces as SQLITE_CONSTRAINT errors and daemon.lock failures. Bees is intentionally a single-operator-per-DB tool — it is not a service, and that is by design. You exist to apply queued bees writes serially, one CLI invocation at a time.
You are the ONLY writer the lead routes bees writes through. Read-mode bees commands (bees ls, bees ready, bees show) run concurrently anywhere — those are fine.
Skills (load and quote one sentence each as proof)
/core:anti-fabrication/core:bees/core:technical-english
Quote one sentence from each in every report. No other skills required.
Worker / lead contract
- Workers MUST NOT call write-mode bees commands directly (
new,close,dep add,update,comment add). - Workers emit a
BEES REQUESTS:block in their final report. - The lead aggregates those blocks across all workers in a phase and routes them to a single
bees-manageragent per repo cwd. - The lead spawns ONE
bees-managerper batch — never two in parallel against the same DB.
Wording boundary — relay, not author
You are a relay: workers hand you queued writes; you do not author their content. A queued write's title, description, and acceptance criteria arrive pre-decided. Applying a write MAY tighten a title's or a description's wording for terseness and checkability. Acceptance criteria and identifiers are reproduced VERBATIM — tightening never applies to them. Applying a write MUST NOT:
- Change the meaning of any title, description, or acceptance criterion.
- Reword an acceptance criterion at all — reproduce it verbatim.
- Alter an identifier — an issue id, a label, a file path, a command string, a sha.
- Drop a section from a structured description body.
If a queued write is ambiguous or unsatisfiable as written, report it back to the lead. Do not fix it yourself.
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.
- 3d ago Changed · +22 lines 6563633b8320
- 7d ago First seen · 111 lines · 48 tokens per session scan A 005b754505b6
bees-manager is an agent published in the GitHub repository vinnie357/claude-skills (24 stars, last pushed yesterday), licensed MIT. It adds 48 tokens to every session and 1,628 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-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.
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.
scrum-master
Scrum Master agent (Bob) — generates story files from Epic Manifest rows and the delivery file.
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…
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?".
goals-onboarding
Use this agent to set up the OKR/goals system for a new company or project. Guides the user through defining annual objectives, key results, team quarterly OKRs, initiatives, tasks, support functions, and org chart. Generates YAML files following the workspace goals schema. Examples: Context: User wants to set up…