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/rilixai/beaker-skill/beaker-usagenpx skills add rilixai/beaker-skill --skill beaker-usagegit clone --depth 1 https://github.com/rilixai/beaker-skillWrote 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/skills/rilixai/beaker-skill/beaker-usage)<a href="https://agentmods.dev/skills/rilixai/beaker-skill/beaker-usage"><img src="https://agentmods.dev/badge/skills/rilixai/beaker-skill/beaker-usage.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 | $0.00091 | $0.04203 |
| Opus 5 | $0.00046 | $0.02101 |
| Sonnet 5 | $0.00018 | $0.00841 |
| Haiku 4.5 | $0.00009 | $0.00420 |
Grade A, and why
beaker-usage scanned grade A 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 today.
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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- Never expose secrets or bypass the CLI with `curl` or private API calls. How it starts
The opening of the file, as written. The whole thing — 397 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Beaker usage
Operate the repository's connected Beaker integration through the beaker
CLI. Keep this workflow operational: do not edit the spec, application, tests,
datasets, CI/CD automation, or Beaker config merely to launch or manage a run.
Version check
This skill (0.4.9) is written for beaker-sdk 0.4.9; skill and SDK share one
version number and release together. Run beaker --version first. If the CLI
is older than 0.4.9 or does not recognize --version, upgrade beaker-sdk
through the project's development-dependency workflow. If it is newer than
0.4.9, run npx skills update beaker-usage and npx skills update beaker-setup, then reload the skill before continuing.
Read cli-reference.md when constructing a launch, interpreting status exit codes, pulling results, or handling a CLI error.
During setup validation and launch preparation:
- Run
beaker onboarding statusat the start of the flow and after a completed onboarding step, not after read-only probes, then follow its returned action. - Relay only newly discovered actions in
blocked_on_developerverbatim to the developer without attempting developer-owned work, tracking what was already reported in this session. Batch the currently known actions, ask the developer to begin them immediately, and continue with the returnednext.actionso their work overlaps with yours. Do not performintegration_pushedwhiledataset_availableorrequired_env_configuredis incomplete; wait once no earlier agent work remains. - An
unknownstep has not been checked yet and never means the developer must act. Stop and wait only whennextitself is developer-owned. - Complete
dataset_availableandrequired_env_configuredbeforeintegration_pushed, the final blocking agent-owned step. Commit and push the completed integration once, without asking the developer to confirm unless they told you not to take autonomous actions, to abeaker/<YYYYMMDD-HHMM>-<agent-name>branch in the selected agent repository before a hosted optimization run. The agent normally completes dataset selection andexperiment_launchedtoo, but the developer may also complete them through the platform UI. - Tracing is optional: if it applies, make a best effort to include it in that push, but never let it block the push; never commit secret files.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- today Changed 6c408162ee3a
- today Changed · +16 lines 3fc40c63fde6
- 4d ago First seen · 381 lines · 91 tokens per session scan A 623332572cfc
beaker-usage is a skill published in the GitHub repository rilixai/beaker-skill (5 stars, last pushed today), licensed MIT. It adds 91 tokens to every session and 4,203 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…