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 commands/aphrody-code/bxc/bxc-new-scrapergit clone --depth 1 https://github.com/aphrody-code/bxcWhat 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.00041 | $0.00239 |
| Opus 5 | $0.00020 | $0.00120 |
| Sonnet 5 | $0.00008 | $0.00048 |
| Haiku 4.5 | $0.00004 | $0.00024 |
Grade A, and why
bxc-new-scraper 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.
What it actually says
Usage: /bxc-new-scraper my-new-site
Steps performed:
- mkdir packages/my-new-site
- Create minimal package.json (name @aphrody/my-new-site, workspace dep on bxc if needed)
- Create src/index.ts with the scraper logic skeleton + export for CLI
- Add a CLI entry in src/cli/my-new-site.ts (export async function main(argv, baseOpts))
- Wire the case in src/cli/index.ts and printUsage
- Add basic test stub in packages/my-new-site/index.test.ts (unit, no live)
- Update root README table if appropriate
- Run the new verify to make sure it doesn't break scoping
Use the bxc-scraper-creator agent for the creative part and bxc-verify-enforcer for the rules.
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.
- 2d ago First seen · 20 lines · 41 tokens per session scan A 8ffd7ab24f7f
bxc-new-scraper is a command published in the GitHub repository aphrody-code/bxc (2 stars, last pushed 2d ago), licensed Apache-2.0. It adds 41 tokens to every session and 239 once invoked, about $0.0002 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 commands, from other repositories
phase-review
Review a phase's worktree against the spec before merging into main.
release
Cut a Uni-CLI release from a clean main.
verify
Run the full Uni-CLI verification gate and report the outcome.
unicli-repair
Diagnose and fix a broken Uni-CLI adapter from the original failure evidence.
unicli-search
Search any supported website or platform using Uni-CLI.
feature
End-to-end feature/bug-sweep workflow for ui-debugger-mcp — understand, reproduce against a real target, explore in parallel, split into path-disjoint slices, build with a hive of agents in this ONE checkout (never worktrees), gate green, PR, merge, release to npm. Tracks in GitHub issues. Reads intent from the prompt.