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 skills add aphrody-code/bxc --skill bxc-coregit clone --depth 1 https://github.com/aphrody-code/bxcWrote 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/aphrody-code/bxc/bxc-core)<a href="https://agentmods.dev/skills/aphrody-code/bxc/bxc-core"><img src="https://agentmods.dev/badge/skills/aphrody-code/bxc/bxc-core/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/aphrody-code/bxc/bxc-core"><img src="https://agentmods.dev/badge/skills/aphrody-code/bxc/bxc-core.svg" alt="Reviewed on agentmods" width="80" 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.00102 | $0.01097 |
| Opus 5.5 | $0.00041 | $0.00439 |
| Sonnet 5.5 | $0.00020 | $0.00219 |
| Haiku 4.5 | $0.00010 | $0.00110 |
Grade A, and why
bxc-core 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 1mo 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 — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.
bxc — Zero-Spawn Native Browser Engine for Agents (toolkit)
bxc is a production-grade, cross-platform (Linux/macOS/Windows) "zero-spawn" navigation engine for AI agents: Bun runtime + Rust cdylib FFI (lol_html, html5ever, V8 bindings, X GraphQL client, For-You ranking algo port) + Zig DOM history in some components. No Chromium spawn for most workloads.
The bxc plugin provides reusable skills, dedicated sub-agents, commands, hooks, and MCP integration so any project can adopt the same architecture, patterns, and quality bars (bxc* naming, scoped testing, native keyless clients, agentic Grok+X loops, monorepo scrapers, autopilot).
Codex integration
When running in Codex, use the .codex-plugin/plugin.json manifest and the
skills/ tree. The bxc-build, bxc-new-scraper, and bxc-verify skills are
the Codex equivalents of the Claude slash commands. Do not depend on Claude
hooks or Claude-only agent invocation; use the available Codex tools and the
global bxc-mcp command instead.
Core Principles (always follow)
- Naming: Every identifier, binary, doc, crate, package must use
bxc*prefix. Rebrand is final — never reintroduce old names. - Test scope: Always
bun test test/ packages/ src/(or more specific). Never barebun test(it discovers vendor/mcp-sdk and produces noise/failures). - Zero keys where possible: Prefer SUPER_GROK_TOKEN / ~/.grok/auth.json for xai, cookie
auth_token+ct0for X (via XSession). No paid API keys for core flows. - Native first: Use the real @aphrody/x XClient and @aphrody/xai Chat + XTools for agentic flows instead of external APIs.
- FFI discipline: Rust cdylibs (bxc-rust-bridge) for hot paths (DOM, ranking, lol_html). Workspace rusqlite 0.37 for sqlite links. Build with
bun run build:linuxor cargo --release. - Cross-platform: Bun works everywhere. Rust produces .so / .dylib / .dll. Provide notes/scripts for all three OS.
- MCP exposure: The bxc-native-mcp (in src/mcp/server.ts) exposes tools; extend with registerTool + Zod. Build to dist/standalone/bxc-mcp.
- Autonomy: The autopilot.sh + monitors + subagents pattern for continuous verify/build/docs.
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.
- 1mo ago Changed · +9 lines e23a633a6592
- 1mo ago First seen · 53 lines · 102 tokens per session scan A 907aa558b5e7
bxc-core is a skill published in the GitHub repository aphrody-code/bxc (3 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 102 tokens to every session and 1,097 once invoked, about $0.0004 per session on Opus 5.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
obscura
Operate and validate Obscura for JavaScript page loading, stealth browsing, anti-fingerprinting, tracker blocking, screenshots and visual comparison, CDP automation with Puppeteer or Playwright, screencasting, PDF export, MCP browser interaction, and web extraction. Use when running Obscura against deterministic…
pinchtab
Use this skill when a task needs browser automation through PinchTab: open a website, inspect interactive elements, click through flows, fill out forms, scrape page text, reuse a dedicated automation profile with user approval, export screenshots or PDFs, manage multiple browser instances, or fall back to the HTTP API…
pinchtab-mcp
Use this skill when a task requires browser automation through PinchTab's MCP server connected to a remote browser instance. Covers navigation, element interaction, data extraction, form filling, multi-step flows, and session management via MCP tools.
browser_harness
../../SKILL.md.
Chrome
Browser automation for the user's Chrome browser. Use for browser tasks that require the user's cookies, logged-in sessions, existing tabs, extensions, or remote authenticated sites.
open-browser-use
Platform-neutral guidance for using Open Browser Use, the open-source Chrome automation stack for AI agents. Use when an agent needs to install, verify, troubleshoot, or operate Open Browser Use through its browser extension, native CLI, JavaScript SDK, Python SDK, Go SDK, or Browser Use style JSON-RPC methods; use…