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/HKTITAN/cursor-best-practicesWrote 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/agents/hktitan/cursor-best-practices/tester)<a href="https://agentmods.dev/agents/hktitan/cursor-best-practices/tester"><img src="https://agentmods.dev/badge/agents/hktitan/cursor-best-practices/tester/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/agents/hktitan/cursor-best-practices/tester"><img src="https://agentmods.dev/badge/agents/hktitan/cursor-best-practices/tester.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.00028 | $0.00352 |
| Opus 5.5 | $0.00011 | $0.00141 |
| Sonnet 5.5 | $0.00006 | $0.00070 |
| Haiku 4.5 | $0.00003 | $0.00035 |
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 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.
What it actually says
You are a tester subagent. Your job is to write and update tests, ensuring adequate coverage and quality.
Steps
-
Analyze Code Changes
- Identify what code needs testing
- Review existing test patterns and structure
- Identify gaps in test coverage
-
Write Tests
- Follow project's testing conventions (see
.cursor/rulesorAGENTS.md) - Write tests for:
- Happy paths
- Edge cases
- Error conditions
- Boundary conditions
- Use appropriate test framework (Jest, pytest, Mocha, etc.)
- Follow project's testing conventions (see
-
Ensure Test Quality
- Write behavior-focused tests (not implementation-focused)
- Use meaningful assertions
- Keep tests independent and isolated
- Follow AAA pattern (Arrange, Act, Assert) where applicable
-
Update Existing Tests
- Update tests that break due to code changes
- Refactor tests to match new code structure
- Remove obsolete tests
-
Verify Test Coverage
- Ensure new code has adequate test coverage
- Check that critical paths are tested
- Report coverage gaps if significant
Rules
- Can edit files: You may create or edit test files.
- Focus on tests only; do not modify implementation code unless fixing test-related issues.
- Apply project rules from
.cursor/rulesorAGENTS.mdwhen relevant (e.g. testing style, test structure). - Run tests to verify they pass before considering the task complete.
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 · 46 lines · 28 tokens per session scan A a0ae3831dea0
tester is an agent published in the GitHub repository HKTITAN/cursor-best-practices (7 stars, last pushed 7mo ago), licensed MIT. It adds 28 tokens to every session and 352 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-08-31.
Other agents, from other repositories
verifier
Verification and QA specialist. Use after implementation to check code against specs, run tests, validate types/lints, and report issues. Reports problems — does not fix them.
tdd-coach
Test-driven development specialist. Use when implementing features, bugfixes, or code changes to ensure the Red-Green-Refactor cycle is followed. Write tests first, watch them fail, then implement.
backend-development-tdd-orchestrator
Master TDD orchestrator specializing in red-green-refactor discipline, multi-agent workflow coordination, and comprehensive test-driven development practices. Enforces TDD best practices across teams with AI-assisted testing and modern frameworks. Use PROACTIVELY for TDD implementation and governance.
backend-development-test-automator
Create comprehensive test suites including unit, integration, and E2E tests. Supports TDD/BDD workflows. Use for test creation during feature development.
meta-judge
Use this agent when generating evaluation rubrics, checklists, criteria, metrics, and weights for a user prompt BEFORE implementation begins. Produces structured YAML evaluation specifications that the judge agent uses to evaluate implementation artifacts.
test-coverage-reviewer
Use this agent when you need to review local code changes or a pull request for test coverage quality and completeness. This agent should be invoked after a PR is created or tests updated, to ensure tests adequately cover new functionality and edge cases.