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/codeready-toolchain/tarsy/create-dashboard-testsgit clone --depth 1 https://github.com/codeready-toolchain/tarsyWrote 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/codeready-toolchain/tarsy/create-dashboard-tests)<a href="https://agentmods.dev/commands/codeready-toolchain/tarsy/create-dashboard-tests"><img src="https://agentmods.dev/badge/commands/codeready-toolchain/tarsy/create-dashboard-tests.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.01032 |
| Opus 5 | $0.00000 | $0.00516 |
| Sonnet 5 | $0.00000 | $0.00206 |
| Haiku 4.5 | $0.00000 | $0.00103 |
Grade A, and why
create-dashboard-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 4d 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 — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Writing Tests for Dashboard Functionality
When to Use This Command
You'll typically use this after implementing new dashboard functionality. Create tests for the complex logic you just added.
CRITICAL: Tests for new functionality often reveal real bugs in the implementation. If a test fails:
- FIRST, analyze if it's a bug in the production code
- FIX THE BUG in the implementation - do NOT write tests that codify incorrect behavior
- Only adjust tests if the implementation is correct and test expectations were wrong
NEVER write tests that document/accept buggy behavior. Tests must verify correct functionality, not enshrine bugs.
If unsure - ASK!
Philosophy: Test What Matters
Write tests that prevent real bugs and give confidence during refactoring. Focus on complex logic prone to breaking.
Test:
- ✅ Complex business logic (parsing, transformations, filters)
- ✅ State management with intricate async flows
- ✅ API services with retry/error handling logic
- ✅ Components with complex conditional logic
Skip:
- ❌ Simple rendering/styling
- ❌ Trivial utilities
- ❌ Framework behavior
- ❌ Tests harder to maintain than the code itself
Coverage is NOT a goal. A few high-quality tests for critical logic beat dozens of brittle ones.
Running Tests
Always use make commands - consistent for humans and CI:
make test-dashboard # Full check: tests + TypeScript (CI)
make dashboard-test # Vitest only (run once)
make dashboard-test-watch # Development (auto-rerun)
make dashboard-test-build # TypeScript check only
make dashboard-lint # Lint dashboard code
make test # All project tests (Go + dashboard)
Test Organization
Place tests in web/dashboard/src/test/:
utils/- Utility function tests (parsers, formatters, persistence)services/- API and auth service testshooks/- Custom hook testscomponents/- Component tests (sparingly!)
Priority Guide
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.
- 4d ago First seen · 117 lines · 0 tokens per session scan A 2e516179f1b3
create-dashboard-tests is a command published in the GitHub repository codeready-toolchain/tarsy (10 stars, last pushed today), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,032 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-31.
Other commands, from other repositories
write-tests
Generate comprehensive test coverage for existing code.
test-tdd
Run when user calls /test-tdd. Scans modified files, locates their corresponding unit/integration test suites, and runs them.
kill-mutants
Analyze surviving mutants from a mutation testing run and write targeted unit tests to kill them. Re-runs mutations to confirm kills.
test
Generate comprehensive tests.
unit-test
Write / run the unit tests for the feature. (AIDLC Unit Test phase) Usage: /unit-test.
test
Execute a comprehensive test run for the following target.