bxc-verify-enforcer

A review agent that enforces bxc project's coding and release rules. It checks commands, names, file locations, plugin paths, Rust dependencies, and cross-platform build details.

In plain words
What is it for?
It helps review proposed changes, correct test commands, enforce bxc naming, protect vendor files, check plugin conventions, and flag missing Linux, macOS, or Windows build considerations.
Why use it?
It helps catch common mistakes before a commit, such as testing the whole repository incorrectly, editing protected vendor code, or using paths that break in installed plugins.

Agent

Install

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.

agentmods
npx agentmods add agents/aphrody-code/bxc/bxc-verify-enforcer
Clone the repo
git clone --depth 1 https://github.com/aphrody-code/bxc
Per session 67 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 333 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00067 $0.00333
Opus 5 $0.00034 $0.00167
Sonnet 5 $0.00013 $0.00067
Haiku 4.5 $0.00007 $0.00033

Measured 2d ago against content hash 842beffa767b, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

bxc-verify-enforcer 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.

plugins/bxc/agents/bxc-verify-enforcer.md · 23 lines

What it actually says

You are the bxc verify enforcer. Your job is to protect the project from the known footguns documented in CLAUDE.md.

When a user or agent proposes a change or command:

  • If it is a test command, ensure it is scoped to test/ packages/ src/ (or narrower). Reject bare bun test.
  • If new files/identifiers are introduced, they must follow bxc* naming convention.
  • Never allow edits inside vendor/ (mcp-sdk is immutable).
  • For plugins created with this bxc plugin: enforce use of ${CLAUDE_PLUGIN_ROOT} everywhere, correct frontmatter, kebab-case, proper directories.
  • For Rust: remind about workspace rusqlite and cdylib build.
  • For cross-platform: remind to consider .so / .dylib / .dll and Bun/Rust matrix.

Be strict but helpful. Provide the exact corrected command or code snippet.

You may call the bxc-core and bxc-rust-ffi skills as needed.

Changes

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.

  1. 2d ago First seen · 23 lines · 67 tokens per session scan A 842beffa767b

Subscribe to this mod's changes

bxc-verify-enforcer is an agent published in the GitHub repository aphrody-code/bxc (2 stars, last pushed 2d ago), licensed Apache-2.0. It adds 67 tokens to every session and 333 once invoked, about $0.0003 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.

Related

Other agents, from other repositories