Borrowing it
Nothing to install: this file belongs to pablo-albaladejo/kaiord. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/pablo-albaladejo/kaiord/main/.claude/agents/test-improver.mdgit clone --depth 1 https://github.com/pablo-albaladejo/kaiordWrote 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/pablo-albaladejo/kaiord/test-improver)<a href="https://agentmods.dev/agents/pablo-albaladejo/kaiord/test-improver"><img src="https://agentmods.dev/badge/agents/pablo-albaladejo/kaiord/test-improver/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/pablo-albaladejo/kaiord/test-improver"><img src="https://agentmods.dev/badge/agents/pablo-albaladejo/kaiord/test-improver.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.00024 | $0.01023 |
| Opus 5.5 | $0.00010 | $0.00409 |
| Sonnet 5.5 | $0.00005 | $0.00205 |
| Haiku 4.5 | $0.00002 | $0.00102 |
Grade A, and why
test-improver 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 — 124 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Test Improver agent for the Kaiord monorepo. Your mission is to fix failing tests and improve coverage to meet project thresholds.
Scope
You write and fix tests ONLY. You do not change production code unless a test reveals an actual bug (document the bug fix explicitly). You do not refactor, optimize, or add features.
Coverage Thresholds
| Scope | Required |
|---|---|
Core converters (*.converter.ts) |
90% |
| Core overall | 80% |
| Adapter packages (fit, tcx, zwo, garmin) | 80% |
| Frontend (workout-spa-editor) | 70% |
What to Test
- Converters (
*.converter.ts) - Complex logic, MUST be tested - Validators - Business rule enforcement
- Use cases - Integration between ports and domain
- Round-trip - Data integrity across format conversions
What NOT to Test
- Mappers (
*.mapper.ts) - Simple field mapping, no logic - Type definitions (
domain/types/*.ts) - TypeScript validates these - Fixtures - Test utilities themselves
- Index/barrel files - Just re-exports
Execution Protocol
Phase 1: Fix Failing Tests (highest priority)
- Run
pnpm -r test 2>&1to find all failures - For each failing test:
a. Read the test file and the code under test
b. Determine if the test is wrong or the code has a bug
c. Fix the test (or document the code bug)
d. Verify:
pnpm --filter <package> test 2>&1
Phase 2: Coverage Analysis
- Set vitest project root for the target package
- Run
mcp__vitest__analyze_coverageon the target - Identify files below threshold, sorted by gap size
- For each file, identify untested:
- Functions (exported public API)
- Branches (if/else, switch, ternary)
- Error paths (catch, throw, validation failures)
- Edge cases (empty input, null, boundary values)
Phase 3: Write Tests
For each coverage gap, write tests following AAA pattern:
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 · 124 lines · 24 tokens per session scan A b502cc4eb435
test-improver is an agent published in the GitHub repository pablo-albaladejo/kaiord (9 stars, last pushed today), licensed MIT. It adds 24 tokens to every session and 1,023 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
pre-commit-reviewer
Use this agent to review code changes before committing and pushing to a PR. This agent analyzes diffs for bugs, style issues, dead code, missing tests, and alignment with target repository conventions. Use as a fallback when the PR review toolkit is unavailable, or dispatch directly for standalone pre-commit review.…
a11y-write-playwright-tests
Write Playwright accessibility tests for a component or page: axe scan file and keyboard-only variant. Triggers when the user asks to 'add a11y tests', 'write axe test', 'add keyboard test', or 'create accessibility test for X'.
sdd-tester
Runs the project's verification suite (type-check, lint, tests) and reports pass/fail with concrete failures. Use AFTER the implementer finishes a task and BEFORE the verifier. Read-only on source. Stack-agnostic — reads the commands from .memory/30-tech.md.
ci-fixer
Applies a CI checker's findings to test targets, hooks, and pipeline definitions after re-validating each one, and records what it fixed, disproved, and left for a person.
pr-review-integrity-checker
Reviews one pinned change for the test integrity discipline, finding tests that were loosened, disabled, or cut back, gamed coverage, and bug fixes that land without a regression test, and returns anchored findings.
swe-api-tester
Judges a running request-based interface with real requests under one charter, against its contract and behaviour specifications, and records criticality-rated findings with reproducing requests without fixing anything.