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.
npx agentmods add skills/nulab/bee/using-beenpx skills add nulab/bee --skill using-beegit clone --depth 1 https://github.com/nulab/beeWhat 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 | $0.00034 | $0.01951 |
| Opus 5 | $0.00017 | $0.00975 |
| Sonnet 5 | $0.00007 | $0.00390 |
| Haiku 4.5 | $0.00003 | $0.00195 |
Grade A, and why
using-bee 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 — 143 lines — stays where its author put it; the contents beside it link to each section on GitHub.
using-bee
bee is a CLI for Backlog. Use it to manage issues, pull requests, projects, wikis, documents, and more.
Prerequisites
bee must be authenticated. If commands fail with auth errors, ask the user to run bee auth login.
Set these environment variables to avoid repeating common flags:
| Variable | Purpose | Example |
|---|---|---|
BACKLOG_SPACE |
Default space hostname | xxx.backlog.com |
BACKLOG_PROJECT |
Default project key | MY_PROJECT |
BACKLOG_REPO |
Default repository name | my-repo |
Commands
| Command | Subcommands |
|---|---|
bee auth |
login, logout, status, token, refresh, switch |
bee project |
list, view, create, edit, delete, users, activities, add-user, remove-user |
bee issue |
list, view, status, create, edit, close, reopen, attachments, comment, count, delete |
bee document |
list, view, tree, attachments, create, delete |
bee notification |
list, count, read, read-all |
bee pr |
list, view, comments, status, create, edit, comment, count |
bee repo |
list, view, clone |
bee team |
list, view |
bee user |
list, view, me, activities |
bee wiki |
list, view, count, tags, history, attachments, create, edit, delete |
bee category |
list, create, edit, delete |
bee milestone |
list, create, edit, delete |
bee issue-type |
list, create, edit, delete |
bee space |
activities |
bee status |
list, create, edit, delete |
bee star |
add, list, count, remove |
bee watching |
list, add, view, delete, read |
bee dashboard |
Show a summary of your Backlog activity |
bee browse |
Open a Backlog page in the browser |
bee api |
Make an authenticated API request |
bee completion |
Generate shell completion scripts |
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 First seen · 143 lines · 34 tokens per session scan A f5241d6aeed4
using-bee is a skill published in the GitHub repository nulab/bee (72 stars, last pushed 2d ago), licensed MIT. It adds 34 tokens to every session and 1,951 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-31.
Other skills, from other repositories
wayfinder
Plan a huge chunk of work (more than one agent session can hold) as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.
setup-matt-pocock-skills
Configure this repo for the engineering skills: set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.
accessibility
Consolidated accessibility skill entrypoint for WCAG 2.2, ARIA Authoring Practices, cognitive accessibility, Section 508, EN 301 549, design intent verification, and the Accessibility Planner workflow.
release-notes
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.
retro
Facilitate a structured sprint retrospective — what went well, what didn't, and prioritized action items with owners and deadlines. Use when running a retrospective, reflecting on a sprint, creating action items from team feedback, or learning how to run effective retros.
bug-triage
Read all open bugs in production/qa/bugs/, re-evaluate priority vs. severity, assign to sprints, surface systemic trends, and produce a triage report. Run at sprint start or when the bug count grows enough to need re-prioritization.