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-levelnpx skills add wilddogjp/openbpx --skill bpx-levelgit 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-level)<a href="https://agentmods.dev/skills/wilddogjp/openbpx/bpx-level"><img src="https://agentmods.dev/badge/skills/wilddogjp/openbpx/bpx-level.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.1 | $0.00025 | $0.00594 |
| Opus 5 | $0.00013 | $0.00297 |
| Sonnet 5 | $0.00005 | $0.00119 |
| Haiku 4.5 | $0.00003 | $0.00059 |
Grade A, and why
bpx-level 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.
How it starts
The opening of the file, as written. The whole thing — 52 lines — stays where its author put it; the contents beside it link to each section on GitHub.
level
PREREQUISITE: Read bpx-shared.
Usage
bpx level info <file.umap> --export <n>
bpx level actor-search <file.umap> [--name <token>] [--actor-label <token>] [--actor-class <token>] [--limit <n>]
bpx level var-list <file.umap> --actor <name|PersistentLevel.Name|export-index>
bpx level var-set <file.umap> --actor <name|PersistentLevel.Name|export-index> --path <dot.path> --value '<json>' [--dry-run] [--backup]
Behavior
info: inspects one level export.actor-search: filters PersistentLevel child exports by name/ActorLabel/ActorClass tokens.var-list: decodes actor properties selected by --actor.var-set: updates one actor property at --path.--actoraccepts object name,PersistentLevel.<Name>, or export index.
[!CAUTION] This command includes write-capable operations. Confirm intent and run
--dry-runfirst.
Command Matrix
| Command | Use when | Notable defaults |
|---|---|---|
info |
inspects one level export. | Read-only path; safe for discovery. |
actor-search |
filters PersistentLevel child exports by name/ActorLabel/ActorClass tokens. | Check bpx help for exact required flags. |
var-list |
decodes actor properties selected by --actor. | Check bpx help for exact required flags. |
var-set |
updates one actor property at --path. | Run --dry-run first and use --backup for real writes. |
Code-Aligned Caveats
--actorresolution supports name,PersistentLevel.<Name>, or export index.var-setuses property path semantics; usevar-listto validate target paths first.
High-Signal Examples
bpx level info ./Sample.umap --export 1
bpx level actor-search ./Sample.umap [--name SampleToken] [--actor-label SampleToken] [--actor-class SampleToken] [--limit 1]
bpx level var-list ./Sample.umap --actor <name|PersistentLevel.Name|export-index>
bpx level var-set ./Sample.umap --actor <name|PersistentLevel.Name|export-index> --path MyProperty --value '{"value":1}' [--dry-run] [--backup]
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 · 52 lines · 25 tokens per session scan A 049c91550fad
bpx-level is a skill published in the GitHub repository wilddogjp/openbpx (99 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 25 tokens to every session and 594 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
gameobject-component-destroy
Destroy one or more Components from a target GameObject. Missing (null) components are skipped — they cannot be destroyed. Use 'gameobject-find' and 'gameobject-component-get' to identify the components first.
unity-version-split
Split a C# file into Unity 6.5+ and pre-Unity 6.5 variants. Use when a file needs different implementations for different Unity versions due to API changes (e.g., EntityId vs int, GetEntityId vs GetInstanceID).
unity-addressables
Manage Addressables groups, entries, profiles and content builds (com.unity.addressables, reflection-based).
playtest-report
Generates a structured playtest report template or analyzes existing playtest notes into a structured format. Use this to standardize playtest feedback collection and analysis.
unity-manual-component
Manually add, configure, reorder, and copy components on GameObjects using Unity Editor UI. For one-off Inspector workflows that do not need REST automation.
godot-signals-groups
Build event-driven, decoupled Godot 4.7 gameplay with signals and node groups: declare and emit custom signals, connect with Callables (incl. bind/one-shot), and broadcast to many nodes via groups and callgroup. Use when wiring node communication in a Godot project, replacing tight references with signals…