Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/armanzeroeight/fastagent-pluginsnpx agentmods add commands/armanzeroeight/fastagent-plugins/run-testsWrote 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/armanzeroeight/fastagent-plugins/run-tests)<a href="https://agentmods.dev/commands/armanzeroeight/fastagent-plugins/run-tests"><img src="https://agentmods.dev/badge/commands/armanzeroeight/fastagent-plugins/run-tests/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/armanzeroeight/fastagent-plugins/run-tests"><img src="https://agentmods.dev/badge/commands/armanzeroeight/fastagent-plugins/run-tests.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.00011 | $0.00694 |
| Opus 5.5 | $0.00004 | $0.00278 |
| Sonnet 5.5 | $0.00002 | $0.00139 |
| Haiku 4.5 | $0.00001 | $0.00069 |
Grade A, and why
run-tests 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 1mo 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 — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Run Tests
Context
- Project type: !
[ -f "package.json" ] && echo "Node.js" || [ -f "pyproject.toml" ] && echo "Python" || [ -f "go.mod" ] && echo "Go" || echo "Unknown" - Test framework: !
[ -f "package.json" ] && (grep -q "jest" package.json && echo "Jest" || grep -q "vitest" package.json && echo "Vitest" || echo "Unknown") || [ -f "pyproject.toml" ] && echo "pytest" || echo "Unknown"
Your Task
Execute tests with appropriate configuration based on the project type and test framework.
Arguments
$1(optional): Test type -unit,integration,e2e, orall(default:all)$2(optional): Additional flags (e.g.,--watch,--coverage,--verbose)
Steps
-
Detect project type and test framework from context above
-
Determine test command based on framework:
Jest:
npm test # or with flags npm test -- --coverage --verboseVitest:
npm run test # or vitest runpytest:
pytest # or with flags pytest -v --cov=srcGo:
go test ./... # or with flags go test -v -cover ./... -
Apply test type filter if specified:
Jest/Vitest (unit tests):
npm test -- --testPathPattern=unitJest/Vitest (integration tests):
npm test -- --testPathPattern=integrationpytest (unit tests):
pytest tests/unit/pytest (integration tests):
pytest tests/integration/Go (specific package):
go test ./pkg/... -
Execute the test command with appropriate flags
-
Report results:
- Number of tests passed/failed
- Execution time
- Coverage percentage (if --coverage flag used)
- Any failing tests with error messages
Examples
Run all tests:
/run-tests
Run unit tests only:
/run-tests unit
Run tests with coverage:
/run-tests all --coverage
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.
- 1mo ago First seen · 118 lines · 11 tokens per session scan A 380ea6baa1bd
run-tests is a command published in the GitHub repository armanzeroeight/fastagent-plugins (29 stars, last pushed 3mo ago), licensed MIT. It adds 11 tokens to every session and 694 once invoked, about $0.0000 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-09-03.
Other commands, from other repositories
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.
qa-pr
Device-test a GitHub pull request on iOS simulator, Android emulator, and/or physical device. Installs the PR head via rn-dev-agent and reports pass/fail with repro steps and screenshots.
run-workflow
Validate and establish the proven rn-dev-agent operating sequence before a real React Native journey — declared package manager and dependencies, read-only inventory, typed session recovery, one exclusive device, managed integration and Metro, only the requested proof, reverse-order cleanup.
lock-e2e
Promote a verified action into a frozen, locked e2e regression test. Runs the action once strict (no repair) via cdplocke2etest and freezes it to .rn-agent/e2e/ .yaml only if it passes. v1 supports param-free actions only.
run-test
Execute AI agent test script in real browser.
user-test
Use /aidd-user-testing to generate human and AI agent test scripts from user journeys.