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/Kazuki-tam/next-stageWrote 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/kazuki-tam/next-stage/quality-check-command)<a href="https://agentmods.dev/commands/kazuki-tam/next-stage/quality-check-command"><img src="https://agentmods.dev/badge/commands/kazuki-tam/next-stage/quality-check-command.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.00381 |
| Opus 5 | $0.00000 | $0.00191 |
| Sonnet 5 | $0.00000 | $0.00076 |
| Haiku 4.5 | $0.00000 | $0.00038 |
Grade A, and why
quality-check-command 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.
What it actually says
quality-check-command
This command performs comprehensive code quality checks. Use it before commits or when implementation is complete.
What It Does
- Code Quality Check: Linting and formatting validation with Biome
- Type Checking: TypeScript type error detection
- Unit Testing: Execute unit tests with Bun test runner
- E2E Testing: Run integration tests with Playwright (optional)
Usage
Running this command will execute the following checks sequentially:
# 1. Code quality check (linting + formatting + type checking)
bun run check
# 2. Unit tests
bun run test:unit
# 3. E2E tests (optional)
# bun run test:e2e
Note: bun run check now includes:
- Biome linting and formatting
- Markuplint validation
- TypeScript type checking (
tsc --noEmit)
Check Items
✅ Code Quality
- Syntax validation with Biome
- Code formatting verification
- Unused import detection
- Naming convention adherence
✅ Type Safety
- TypeScript strict mode validation
- Type error detection
- Type inference verification
✅ Testing
- Run all unit tests
- Test coverage validation
- E2E test execution (critical paths)
Error Resolution
Steps to resolve detected errors:
- Linting Errors: Try auto-fix with
bun run format - Type Errors: Check the location in your editor and fix type definitions
- Test Failures: Review test logs and fix the corresponding code
Recommended Usage
- ✅ After feature implementation
- ✅ Before commits
- ✅ Before creating pull requests
- ✅ Before deployment
This command is available in chat as /quality-check-command.
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 · 66 lines · 0 tokens per session scan A 1e68f14517c1
quality-check-command is a command published in the GitHub repository Kazuki-tam/next-stage (12 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 381 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
pr-enhance
Command "pr-enhance" from ruvnet/ruflo, covering pr-enhance, usage, options, examples and enhance pr.
gsd:add-tests
Generate tests for a completed phase based on UAT criteria and implementation.
testing
Comprehensive testing through distributed execution.
verify
You are invoking the verify skill - comprehensive verification following Boris Cherny's pattern.
test
Escrever e rodar testes (skill 05 — QA Engineer).
test
Load the testing strategies skill for 3-tier testing with NO MOCKING policy enforcement in Tier 2-3.