Borrowing it
Nothing to install: this file belongs to Consensys/ask-o11y-plugin. 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/Consensys/ask-o11y-plugin/main/.cursor/commands/run-all-tests-and-fix.mdgit clone --depth 1 https://github.com/Consensys/ask-o11y-pluginWrote 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/consensys/ask-o11y-plugin/run-all-tests-and-fix)<a href="https://agentmods.dev/commands/consensys/ask-o11y-plugin/run-all-tests-and-fix"><img src="https://agentmods.dev/badge/commands/consensys/ask-o11y-plugin/run-all-tests-and-fix/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/consensys/ask-o11y-plugin/run-all-tests-and-fix"><img src="https://agentmods.dev/badge/commands/consensys/ask-o11y-plugin/run-all-tests-and-fix.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.00000 | $0.00816 |
| Opus 5 | $0.00000 | $0.00408 |
| Sonnet 5 | $0.00000 | $0.00163 |
| Haiku 4.5 | $0.00000 | $0.00082 |
Grade A, and why
run-all-tests-and-fix 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 10d 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 — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Run All Tests and Fix Failures
Overview
Execute the full test suite and systematically fix any failures, ensuring code quality and functionality. All test-related commands must pass before completion.
Test Commands
Run these commands in order. All must pass:
# 1. Unit tests (Jest)
npm run test:ci
# 2. TypeScript type checking
npm run typecheck
# 3. Linting (ESLint)
npm run lint
# 4. E2E tests (Playwright) - requires running server
npm run e2e
Execution Steps
1. Run the Full Test Suite
Execute all test commands sequentially:
npm run test:ci && npm run typecheck && npm run lint && npm run e2e
Requirements:
- All commands must exit with code 0
- No test should be skipped unless marked with
// IMPORTANT: <reason>comment - If a test uses
test.skip()without anIMPORTANTcomment, fix the test so it runs - Warnings are acceptable; errors are not
2. Analyze Failures
For each failure, determine:
| Category | Description | Priority |
|---|---|---|
| Type Error | TypeScript compilation failure | High |
| Lint Error | ESLint rule violation | Medium |
| Unit Test | Jest test failure | High |
| E2E Test | Playwright test failure | High |
| Flaky | Intermittent failures | Medium |
Investigation checklist:
- Check if the failure is in test code or source code
- Look for recent changes that might have caused it
- Check error context files in
test-results/for E2E failures - Review console output for stack traces
3. Fix Issues Systematically
Order of operations:
- Fix TypeScript errors first (blocks other tests)
- Fix ESLint errors second
- Fix unit test failures
- Fix E2E test failures last
For each fix:
- Make the minimal change needed
- Re-run the specific test to verify
- Run full suite before moving to next issue
4. Handle Skipped Tests
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.
- 10d ago First seen · 113 lines · 0 tokens per session scan A 2a37886a1599
run-all-tests-and-fix is a command published in the GitHub repository Consensys/ask-o11y-plugin (41 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 816 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-suite
Run comprehensive test suite with coverage analysis.
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.