Borrowing it
Nothing to install: this file belongs to IgorGanapolsky/openclaw-console. 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/IgorGanapolsky/openclaw-console/develop/.claude/commands/testing.mdgit clone --depth 1 https://github.com/IgorGanapolsky/openclaw-consoleWrote 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/igorganapolsky/openclaw-console/testing)<a href="https://agentmods.dev/commands/igorganapolsky/openclaw-console/testing"><img src="https://agentmods.dev/badge/commands/igorganapolsky/openclaw-console/testing/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/igorganapolsky/openclaw-console/testing"><img src="https://agentmods.dev/badge/commands/igorganapolsky/openclaw-console/testing.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.00025 | $0.00254 |
| Opus 5.5 | $0.00010 | $0.00102 |
| Sonnet 5.5 | $0.00005 | $0.00051 |
| Haiku 4.5 | $0.00003 | $0.00025 |
Grade A, and why
testing 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 26d 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
Testing
Run the appropriate test suite based on what changed.
Steps
- Detect changed files:
git diff --name-only HEAD~1
- Run platform-specific tests:
Android (if android/ files changed):
cd android && ./gradlew testDebugUnitTest --no-daemon
iOS (if ios/ files changed):
cd ios/OpenClawConsole && xcodebuild -scheme OpenClawConsole \
-destination 'platform=iOS Simulator,name=iPhone 16' \
-configuration Debug test CODE_SIGNING_ALLOWED=NO 2>&1 | tail -30
Skills (if openclaw-skills/ files changed):
cd openclaw-skills && npm test
- Report results:
pass: test name, count, timefail: test name, file:line, error, suggested fix
- If all pass:
All tests passed (N in Ts)
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.
- 26d ago First seen · 41 lines · 25 tokens per session scan A 26f4a7919880
testing is a command published in the GitHub repository IgorGanapolsky/openclaw-console (6 stars, last pushed 1mo ago), licensed MIT. It adds 25 tokens to every session and 254 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-10-02.
Other commands, from other repositories
feature-test
Create all tests for an implemented feature - unit tests (ViewModel, UseCase, Repository), Compose UI tests, and E2E user flow tests.
test-suite
Run comprehensive test suite with coverage analysis.
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.
ux-grill
Use when a running web app's UX has to be audited reproducibly rather than by feel — a deterministic mechanical pass over routes and viewports (axe, target size, horizontal overflow, page title, scripted journeys) followed by a screenshot-grounded interrogation of the operator, journey by journey, with two persona…
test
Escrever e rodar testes (skill 05 — QA Engineer).
quality-check-command
This command performs comprehensive code quality checks. Use it before commits or when implementation is complete.