AIHelms is an enterprise platform for managing AI resources through a unified gateway, including model access, identities, budgets, usage costs, security reviews, MCP tools, and agent skills. Organizations use it to control AI spending, govern access, audit activity, and measure usage and value across teams. Its catalogue add-ons support operating and administering the platform’s AI management workflows.
Borrowing it
Nothing to install: this file belongs to beizhu-1209/AIHelms. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/beizhu-1209/AIHelms/main/.claude/commands/test.mdgit clone --depth 1 https://github.com/beizhu-1209/AIHelmsWrote 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/beizhu-1209/aihelms/test)<a href="https://agentmods.dev/commands/beizhu-1209/aihelms/test"><img src="https://agentmods.dev/badge/commands/beizhu-1209/aihelms/test.svg" alt="Measured on agentmods" 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.00000 | $0.01047 |
| Opus 5 | $0.00000 | $0.00524 |
| Sonnet 5 | $0.00000 | $0.00209 |
| Haiku 4.5 | $0.00000 | $0.00105 |
Grade A, and why
test 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 7d 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.
The source is not reproduced here
Licensed GPL-3.0
The repository is licensed GPL-3.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.
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.
- 7d ago First seen · 188 lines · 0 tokens per session scan A 0ee4997ea02d
test is a command published in the GitHub repository beizhu-1209/AIHelms (1,029 stars, last pushed 3d ago), licensed GPL-3.0. It costs nothing until one of its globs matches a file; then it loads 1,047 tokens. 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
test-driven-development
Use when implementing any feature or bugfix, before writing implementation code - write the test first, watch it fail, write minimal code to pass; ensures tests actually verify behavior by requiring failure first.
webapp-testing
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
test-feature
Test a React Native feature on the running simulator/emulator. Verifies UI, user flows, and internal state. Generates a persistent Maestro test file.
coverage-report
Generate and display test coverage report with analysis and recommendations.
check-go
Run Go code quality checks including formatting, linting, vetting, and tests.
bug-check
Run automated tests and build checks first, then agent code review. For each bug found, propose or document a regression test.