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/hamchowderr/braynee/pournpx skills add hamchowderr/braynee --skill pourgit clone --depth 1 https://github.com/hamchowderr/brayneeWhat 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.00096 | $0.01039 |
| Opus 5 | $0.00048 | $0.00519 |
| Sonnet 5 | $0.00019 | $0.00208 |
| Haiku 4.5 | $0.00010 | $0.00104 |
Grade A, and why
pour 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 2d 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 — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pour — beads workflow formula launcher
Formulas are recipes for multi-step work. bd mol pour <formula> creates
the whole molecule of linked, gated beads issues in one shot — no manual
bd create / bd dep add sequence.
This skill is the friendly menu in front of that command. It picks the formula, collects the vars via AskUserQuestion, dry-runs first to confirm, then pours for real.
Available formulas (canonical)
Always re-list with bd formula list before showing the user — formulas
can be added or removed.
| Formula | Use when |
|---|---|
| project | Your own work. Internal projects, no client coordination. 4 steps: scope → build → qa → ship. |
| engagement | Paid client work. 7 steps: discovery → scope → build → qa → review → ship → handoff. Two human gates (discovery, review). |
| braynee-release | Shipping a new braynee plugin version. 4 steps: selftest → sandbox → deploy-cache → bump. No PR. |
Workflow
1. Pick a formula
- If the user passed an argument (
/braynee:pour engagement), use that. - Otherwise call
bd formula listto show the live list, then use AskUserQuestion to ask which one.
2. Show what it does, then collect vars
- Run
bd formula show <name>so the user can see the steps and vars before they commit. - Use AskUserQuestion to collect each required var. Mark optional vars as such — let the user skip them.
Required vars per formula (verify with bd formula show — this is a
quick reference, the formula files are authoritative):
| Formula | Required | Optional |
|---|---|---|
| project | name, deliverable |
— |
| engagement | client, deliverable |
reference |
| braynee-release | version (semver X.Y.Z) |
— |
3. Dry-run first
ALWAYS dry-run before pouring for real:
bd mol pour <formula> --var key="value" ... --dry-run
Show the list of issues that would be created. Ask the user to confirm
before re-running without --dry-run.
4. Pour for real
On confirmation, drop --dry-run:
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.
- 2d ago First seen · 113 lines · 96 tokens per session scan A ed8e90f68068
pour is a skill published in the GitHub repository hamchowderr/braynee (2 stars, last pushed 6d ago), licensed MIT. It adds 96 tokens to every session and 1,039 once invoked, about $0.0005 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
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…