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 allxsmith/bestax --skill bestax-migrategit 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/skills/allxsmith/bestax/bestax-migrate)<a href="https://agentmods.dev/skills/allxsmith/bestax/bestax-migrate"><img src="https://agentmods.dev/badge/skills/allxsmith/bestax/bestax-migrate/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/allxsmith/bestax/bestax-migrate"><img src="https://agentmods.dev/badge/skills/allxsmith/bestax/bestax-migrate.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Prompt Injection · line 18 Large whitespace padding was detected (a block of blank lines or a long run of spaces). This can push injected instructions below or to the right of the visible area so a human reviewer never sees them while the agent still reads them. Manual review of the hidden content is recommended.Fix: Remove the large whitespace padding (blank-line blocks or long space runs) and review any content hidden below or to the right of it. Keep skill files compact and reviewable so no instructions can be
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.00147 | $0.01995 |
| Opus 5 | $0.00073 | $0.00997 |
| Sonnet 5 | $0.00029 | $0.00399 |
| Haiku 4.5 | $0.00015 | $0.00199 |
Grade A, and why
bestax-migrate 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 3d 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 — 125 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Migrating to bestax-bulma
@allxsmith/bestax-bulma is an actively maintained React library for Bulma v1. The
bestax-migrate codemod automates most of the conversion from an unmaintained predecessor;
this skill drives the codemod and finishes what it flags.
Pick the source
The codemod's first argument names the library you are migrating from. Check the app's
package.json and imports:
| Source | Argument | References |
|---|---|---|
react-bulma-components v4 (unmaintained since 2022, Bulma 0.9.x) |
react-bulma-components |
references/react-bulma-components/ |
rbx v2 (abandoned 2019, pins Bulma 0.7.5 plus four extensions) |
rbx |
references/rbx/ |
bloomer 0.6 (archived 2018, Bulma 0.6 era, React 16 + create-react-class) |
bloomer |
references/bloomer/ |
Everything below is written as <source>; substitute the argument from that table. The
reference paths follow the same split — references/<source>/component-map.md,
prop-map.md, unmappables.md — while
references/css-migration.md is shared, because the stylesheet
work is about Bulma, not about which wrapper you came from.
Workflow
Run these steps in order. Don't hand-convert what the codemod converts automatically.
-
Dry-run the codemod on the source directory and review the report:
pnpm dlx bestax-migrate <source> src/ --dry
What ships with it
10 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- references/bloomer/component-map.md 12 KB
- references/bloomer/prop-map.md 22 KB
- references/bloomer/unmappables.md 13 KB
- references/css-migration.md 8.4 KB
- references/rbx/component-map.md 12 KB
- references/rbx/prop-map.md 10 KB
- references/rbx/unmappables.md 11 KB
- references/react-bulma-components/component-map.md 13 KB
- references/react-bulma-components/prop-map.md 6.2 KB
- references/react-bulma-components/unmappables.md 6.6 KB
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.
- 3d ago Changed · +12 lines · +10 tokens per session ac3cd1b17ad1
- 5d ago Changed · +34 lines · +22 tokens per session a8250a15bae7
- 9d ago First seen · 79 lines · 115 tokens per session scan A 83dbe656a8c7
bestax-migrate is a skill published in the GitHub repository allxsmith/bestax (11 stars, last pushed yesterday), licensed MIT. It adds 147 tokens to every session and 1,995 once invoked, about $0.0007 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
magic-ui
Use this skill when users want to add, customize, or troubleshoot Magic UI components in React/Next.js projects. It covers component selection, shadcn registry installation (@magicui/), integration patterns, and practical quality checks for accessibility and maintainability.
frontend-ai-guide
Applies React/TypeScript-specific technical decision criteria, anti-pattern detection, debugging, and frontend quality gates. Use when reviewing components, hooks, browser behavior, or frontend implementation completeness.
typescript-rules
React/TypeScript frontend development rules including type safety, component design, state management, and error handling. Use when implementing React components, TypeScript code, or frontend features.
frontend-technical-spec
Defines React environment, component architecture, state/data flow, build verification, and frontend non-functional criteria from repository evidence. Use when configuring or designing a React frontend, its build, or its runtime boundaries.
frontend-typescript-rules
Applies React/TypeScript type safety, component design, and state management rules. Use when implementing React components.
stitch-react-components
Convert Stitch HTML and screenshots into modular Vite/React/TypeScript components, or sync existing components to updated Stitch designs, with local architecture and validation checks.