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.
git clone --depth 1 https://github.com/allxsmith/bestaxWrote 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/commands/allxsmith/bestax/pre-pr)<a href="https://agentmods.dev/commands/allxsmith/bestax/pre-pr"><img src="https://agentmods.dev/badge/commands/allxsmith/bestax/pre-pr/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/commands/allxsmith/bestax/pre-pr"><img src="https://agentmods.dev/badge/commands/allxsmith/bestax/pre-pr.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.00021 | $0.00357 |
| Opus 5.5 | $0.00008 | $0.00143 |
| Sonnet 5.5 | $0.00004 | $0.00071 |
| Haiku 4.5 | $0.00002 | $0.00036 |
Grade A, and why
pre-pr 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.
What it actually says
/pre-pr — gate + self-review before opening a PR
- Run
pnpm all(build, typecheck, test+coverage, bundle:stats, lint, format:check, storybook build). If it fails, report the failing task and stop — fix before reviewing. - Read the working diff (
git status,git diff main...HEADplus any uncommitted changes). If the diff touchesbulma-ui/srccomponents, stories, SCSS, orskills/, review it against the checklist inCONTRIBUTING-COMPONENTS.md(repo root — Read it), focusing on what CI can NOT catch:- prop-level changes without matching story/docs/skills updates
- missing listing surfaces (guide page section, homepage card — step 2)
- skills sync for themeable or shared-helper changes (step 3)
For diffs that don't touch components (docs-only, tooling, workflows),
SKIP the component checklist and just review the diff generally.
Always check commit message type/scope (
feat|fix|perf|refactor|styleneed scopebulma-ui|docs|create-bestax).
- Report a short summary: gate result, then each checklist gap with the file to touch. Do not fix anything — this command only reviews.
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 First seen · 25 lines · 21 tokens per session scan A e97fc932311f
pre-pr is a command published in the GitHub repository allxsmith/bestax (12 stars, last pushed today), licensed MIT. It adds 21 tokens to every session and 357 once invoked, about $0.0001 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-30.
Other commands, from other repositories
quality-commands
:::info This document covers all code quality commands for the eIsland project — ESLint, Stylelint, HTML validation, comment checks, and i18n completeness. ::.
finn
Invoke Finn, your Senior Frontend Developer for React, Next.js, React Native, TypeScript, and TailwindCSS implementation.
code-review
Run an AI-assisted PR code review using multi-layer lenses with confidence scoring.
code-quality-review
Audit code quality (clean-code/DRY/KISS) and report by severity — no edits.
review-code
Read ALL memory bank code rules + best practices, check the files that changed, and APPLY fixes so they adhere. The active counterpart to /scan (which is read-only). Use after an AI session, before commit, to make changed files compliant.
e2e-testing
:::info The Playwright suite launches the real Electron main process and built React UI on Windows and macOS. It exercises the preload bridge, IPC handlers, and file storage. See Testing Commands for the separate Vitest suite. ::.