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/masonegger/bpe-claude-code-plugin/goalnpx skills add MasonEgger/bpe-claude-code-plugin --skill goalgit clone --depth 1 https://github.com/MasonEgger/bpe-claude-code-pluginWrote 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/masonegger/bpe-claude-code-plugin/goal)<a href="https://agentmods.dev/skills/masonegger/bpe-claude-code-plugin/goal"><img src="https://agentmods.dev/badge/skills/masonegger/bpe-claude-code-plugin/goal.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.00126 | $0.03638 |
| Opus 5 | $0.00063 | $0.01819 |
| Sonnet 5 | $0.00025 | $0.00728 |
| Haiku 4.5 | $0.00013 | $0.00364 |
Grade A, and why
goal 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 — 174 lines — stays where its author put it; the contents beside it link to each section on GitHub.
BPE Autonomous Goal
Set up a /goal-driven autonomous BPE run. The parent session orchestrates; each step is executed by the bpe:step-executor subagent in modes (implement, optional fix loop, finalize). When the step's plan.md section declares validators, bpe:validator runs between implement and finalize and the orchestrator drives the fix loop (max 3 iterations) per ${CLAUDE_PLUGIN_ROOT}/references/validator-protocol.md. Fresh context per dispatch; the parent transcript stays tiny; the /goal evaluator watches it for completion.
Requires Claude Code v2.1.139+. Pairs well with /auto. The /goal command itself must still be run by the user; slash commands cannot invoke other slash commands programmatically, so this command writes the assembled /goal invocation to goal.md at the repo root and you paste it from there.
Mode Routing
Parse $ARGUMENTS:
- empty or
full: autonomous to the end oftodo.md. Default. Use when you trust the plan and have time / quota. section <name>: autonomous through one labeled section oftodo.md. A section is a top-level Markdown heading or an explicit comment block like<!-- section: foo -->.step: autonomous through ONE step. Rarely the right tool; for a single interactive step,/bpe:execute-planis simpler. Usesteponly when you want the autonomous-mode contracts (SHA verification, session-summary-per-commit, push, validator pass) on a single item without driving it yourself.
State the routed mode in user-facing text before pre-flight.
Step 1: Pre-Flight Checks (refuse on any failure)
Run these in parallel and surface results in user-facing text:
git rev-parse --abbrev-ref HEAD
git status --short
test -f plan.md && echo "plan: yes" || echo "plan: NO"
test -f todo.md && echo "todo: yes" || echo "todo: NO"
grep -c '^- \[ \]' todo.md 2>/dev/null || echo 0
grep -q '^commit-msg\.md$' .gitignore && echo "gitignore commit-msg.md: ok" || echo "gitignore commit-msg.md: MISSING"
grep -q '^goal\.md$' .gitignore && echo "gitignore goal.md: ok" || echo "gitignore goal.md: MISSING"
grep -cE '^\*\*(Tools|Validator consults):\*\*' plan.md 2>/dev/null || echo 0
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 First seen · 174 lines · 126 tokens per session scan A 18aa89eda7b7
goal is a skill published in the GitHub repository MasonEgger/bpe-claude-code-plugin (7 stars, last pushed 11d ago), licensed MIT. It adds 126 tokens to every session and 3,638 once invoked, about $0.0006 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…