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/wilddogjp/openbpx/bpx-sharednpx skills add wilddogjp/openbpx --skill bpx-sharedgit clone --depth 1 https://github.com/wilddogjp/openbpxWrote 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/wilddogjp/openbpx/bpx-shared)<a href="https://agentmods.dev/skills/wilddogjp/openbpx/bpx-shared"><img src="https://agentmods.dev/badge/skills/wilddogjp/openbpx/bpx-shared.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.00021 | $0.00424 |
| Opus 5 | $0.00010 | $0.00212 |
| Sonnet 5 | $0.00004 | $0.00085 |
| Haiku 4.5 | $0.00002 | $0.00042 |
Grade A, and why
bpx-shared 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 5d 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.
What it actually says
bpx shared
Installation
- Prefer
bpxfromPATHwhen available. - Plugin installs include a bundled fallback wrapper at
../../bin/bpx(or../../bin/bpx.cmdon Windows) relative to this skill. - Confirm with
<bpx-command> versionand<bpx-command> help; use the same resolved command in later examples.
Safety Rules
- Treat assets as untrusted binary input.
- Prefer read commands before write commands.
- Run
--dry-runfirst for write-capable commands. - Use
--backupwhen writing files in place.
Standard Workflow
- Inspect command shape with
bpx help <command>. - Identify exact targets using read commands.
- Run write command with
--dry-run. - Execute real write with
--backupwhen approved. - Validate with
bpx validate <file> --binary-equalityas needed.
Global Rules
- Prefer read commands before write commands.
- Use
--dry-runfirst for write-capable commands. - Use
--backupfor in-place updates unless explicitly declined. - For automation, prefer
--format tomlwhere available.
Command Selection Heuristics
- Package shape/version checks:
info,dump,validate. - Export/import and reference analysis:
export,import,ref,raw. - Gameplay/content edits:
prop,var,datatable,localization,stringtable,level. - Blueprint analysis workflow:
blueprint info->blueprint disasm->blueprint trace/search.
Output Reading Tips
- Treat warnings as actionable signals; they often indicate partial decode paths.
- For write responses, inspect changed-byte and size-delta fields before applying.
- On errors, re-run
bpx help <command>to confirm required flags and accepted forms.
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.
- 5d ago First seen · 48 lines · 21 tokens per session scan A f167b33f3439
bpx-shared is a skill published in the GitHub repository wilddogjp/openbpx (99 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 21 tokens to every session and 424 once invoked, about $0.0001 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 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…