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.
git 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-backend-tests)<a href="https://agentmods.dev/commands/codeready-toolchain/tarsy/create-backend-tests"><img src="https://agentmods.dev/badge/commands/codeready-toolchain/tarsy/create-backend-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/codeready-toolchain/tarsy/create-backend-tests"><img src="https://agentmods.dev/badge/commands/codeready-toolchain/tarsy/create-backend-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.00000 | $0.01327 |
| Opus 5.5 | $0.00000 | $0.00531 |
| Sonnet 5.5 | $0.00000 | $0.00265 |
| Haiku 4.5 | $0.00000 | $0.00133 |
Grade A, and why
create-backend-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 — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Writing Tests for Go Backend
Running Tests
From Project Root
All tests:
make test- Run all tests (Go + Python)make test-go- Run all Go tests (unit + e2e)make test-unit- Run Go unit/integration tests onlymake test-e2e- Run Go e2e tests onlymake test-go-coverage- Run Go tests and open HTML coverage report
Direct Go Commands
- Specific package:
go test ./pkg/queue/... -v - Specific test:
go test ./pkg/api -run TestExtractAuthor -v - With coverage:
go test -v -race -coverprofile=coverage.out ./... - Race detector:
go test -race ./...(always use for concurrent code) - Show coverage:
go tool cover -html=coverage.out
Critical Rules
1. Be Pragmatic
Write tests that add real value. If a test requires overly complex mocking or doesn't validate meaningful behavior, skip it. It's better to have no test than a brittle one that breaks with every minor change. If fighting with mocks, consider an integration test instead.
2. Test Behavior, Not Implementation
Focus on what the code does, not how. Don't test that specific internal methods were called or verify exact sequences of internal function calls.
3. No Historical Comments in Code
No // Added in TASK-0025 or // Testing new implementation. Historical context belongs in git commits. Tests should be self-explanatory.
4. Extend Existing Tests Before Creating New Ones
When code already has test coverage, prefer modifying or extending existing tests to cover new behavior rather than creating new test functions that largely duplicate what's already there. Add cases to existing table-driven tests when the scenario fits.
5. All Tests Must Pass
New tests are done ONLY when they ALL pass 100%. Don't leave failing tests. If a test is too complex to get right, don't write it.
6. No Documentation Files Unless Explicitly Requested
DO NOT create summary documents, README files, or any markdown documentation files (like test coverage summaries, test reports, etc.) unless the user explicitly asks for them. Focus exclusively on creating the actual test code.
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 · 99 lines · 0 tokens per session scan A a13d88199219
create-backend-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,327 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
aqe-generate
Generate comprehensive test suites using AI-powered analysis and sublinear optimization.
testing
Comprehensive testing through distributed execution.
verify
Grade work that already exists and decide whether it can merge. Runs the project's current unit, integration, and E2E suites plus security scanning and type checking, scores every dimension 0-10, and returns a merge verdict with a VERIFIED-vs-CLAIMED evidence manifest. Writes no test files and edits no source. Use…
test-suite
Run comprehensive test suite with coverage analysis.
cover
Generate tests that do not exist yet. Analyzes coverage gaps, then writes and runs new test files across three tiers (unit, integration via testcontainers, Playwright E2E), one test-generator agent per tier, healing failures for up to 3 iterations. Use when code has no tests or when raising coverage after…
devkit.java.write-integration-tests
Generates comprehensive integration tests for Spring Boot classes using Testcontainers (PostgreSQL, Redis, MongoDB) with @ServiceConnection pattern. Use when writing integration tests for service or repository classes.