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.
npx agentmods add commands/f-amine/vibe-stack/testergit clone --depth 1 https://github.com/f-amine/vibe-stackWrote 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/f-amine/vibe-stack/tester)<a href="https://agentmods.dev/commands/f-amine/vibe-stack/tester"><img src="https://agentmods.dev/badge/commands/f-amine/vibe-stack/tester.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 | $0.00000 | $0.00263 |
| Opus 5 | $0.00000 | $0.00131 |
| Sonnet 5 | $0.00000 | $0.00053 |
| Haiku 4.5 | $0.00000 | $0.00026 |
Grade A, and why
tester 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 today.
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.
This is a copy
100% identical to tester — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
SPARC Tester Mode
Purpose
Comprehensive testing with parallel execution capabilities.
Activation
Option 1: Using MCP Tools (Preferred in Claude Code)
mcp__claude-flow__sparc_mode {
mode: "tester",
task_description: "full regression suite",
options: {
parallel: true,
coverage: true
}
}
Option 2: Using NPX CLI (Fallback when MCP not available)
# Use when running from terminal or MCP tools unavailable
npx claude-flow sparc run tester "full regression suite"
# For alpha features
npx claude-flow@alpha sparc run tester "full regression suite"
Option 3: Local Installation
# If claude-flow is installed locally
./claude-flow sparc run tester "full regression suite"
Core Capabilities
- Test planning
- Test execution
- Bug detection
- Coverage analysis
- Report generation
Test Types
- Unit tests
- Integration tests
- E2E tests
- Performance tests
- Security tests
Parallel Features
- Concurrent test runs
- Distributed testing
- Load testing
- Cross-browser testing
- Multi-environment validation
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.
- today First seen · 55 lines · 0 tokens per session scan A 5938dfcb7e80
tester is a command published in the GitHub repository f-amine/vibe-stack (21 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 263 tokens. A static security scan graded it A with 0 findings. It is 100% identical to tester, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
add
Add addons/features (PWA, Tauri, docs, linters, task runners, MCP, …) to an existing Better-T-Stack project via the Better-T-Stack MCP server.
test-design
Design test coverage strategy with test-architect guidance.
odoo-test
Odoo testing toolkit - generate, mock data, run, coverage, and E2E tests.
generate-tests
Generate tests for changed files — unit tests for functions, integration tests for APIs, E2E for user flows.
OPSX: Propose
Propose a new change - create it and generate all artifacts in one step.
6-test
Full Test Suite Execution: Run complete test suite (unit, integration, e2e, evaluation, metrics, performance) to validate all fixes and ensure system reliability. Verify all quality gates pass before proceeding.