Borrowing it
Nothing to install: this file belongs to timohaa/scopewalker-mcp. 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/timohaa/scopewalker-mcp/main/.claude/agents/smart-test-fixer.mdgit clone --depth 1 https://github.com/timohaa/scopewalker-mcpWrote 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/timohaa/scopewalker-mcp/smart-test-fixer)<a href="https://agentmods.dev/agents/timohaa/scopewalker-mcp/smart-test-fixer"><img src="https://agentmods.dev/badge/agents/timohaa/scopewalker-mcp/smart-test-fixer.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.1 | $0.00028 | $0.00667 |
| Opus 5 | $0.00014 | $0.00333 |
| Sonnet 5 | $0.00006 | $0.00133 |
| Haiku 4.5 | $0.00003 | $0.00067 |
Grade A, and why
smart-test-fixer 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 3d 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 — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Smart Test Fixer Agent
Run the TypeScript project checks and tests. Diagnose and fix every warning, error, and test failure.
Workflow
1. Run Initial Checks
npm run check 2>&1
npm run test 2>&1
If your prompt states that lint/typecheck was already verified green, skip the initial
npm run check and run it only after you edit source files.
2. Categorize Issues
Group findings into:
- TypeScript/lint warnings
- TypeScript/lint errors
- Test failures
- Runtime errors
3. Understand Recent Changes
Before fixing failing tests, check git log --oneline -10 and git diff to understand:
- What code was recently changed and why
- Whether test failures are due to intentional behavior changes
- The developer's intent behind recent modifications
4. Determine Fix Strategy
For each issue, decide whether to fix the source code or the test.
Decision Framework
Fix the CODE when
- The test correctly validates expected behavior
- The code change was accidental or introduced a regression
- Recent changes don't indicate intentional behavior modification
Fix the TEST when
- Recent changes indicate intentional behavior changes
- Test assertions are outdated or incorrect
- The test is testing implementation details that legitimately changed
Resolution Order
Fix in dependency order:
- Type errors: these often cascade into other issues
- Lint errors: run
npm run lint:fixfor auto-fixable, then fix remaining manually - Test failures: fix after source code is stable
Iteration Protocol
- After each batch of fixes, re-run only the affected test files in one
invocation (
npx vitest run a.test.ts b.test.ts), plusnpm run checkif source files changed. Not the full suite. Run a single test file alone only to diagnose one failure. - Continue until the targeted tests and checks pass with zero warnings and zero failures
- Run the full
npm run check && npm run testonce as final confirmation before reporting - Report using the Output Format below
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.
- 3d ago Changed · -22 tokens per session 0d46dee81314
- 6d ago First seen · 96 lines · 50 tokens per session scan A a0d9262deec8
smart-test-fixer is an agent published in the GitHub repository timohaa/scopewalker-mcp (0 stars, last pushed 3d ago), licensed MIT. It adds 28 tokens to every session and 667 once invoked, about $0.0001 per session on Opus 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
test-case-result-validator
Compares old vs new instruction outputs against original codebase, scores 8 quality categories, emits pass/fail JSON verdict for CI/CD validation pipeline.
timps_red_team_agent
Plan and execute an OWASP-style red-team engagement: threat model, adversarial test cases, payloads, runnable exploit harness, and a remediation checklist. Use the timpsredteamagent MCP tool to perform this task. Do not answer directly — delegate to this sub-agent.
timps_test_data_agent
Generate realistic, edge-case-covering seed / fixture data for any JSON schema, SQL DDL, or plain-text description. Use the timpstestdataagent MCP tool to perform this task. Do not answer directly — delegate to this sub-agent.
step-generator
Generate test steps from natural language descriptions. Use when: (1) User describes a test scenario in plain English, (2) Complex UI interactions need step-by-step breakdown, (3) User wants to add steps but doesn't know the exact format.
test-analyzer
Deep analysis of E2E test failures and results. Use when: (1) A test has failed and needs root cause analysis, (2) User wants to understand why a step failed, (3) Complex multi-step failures need investigation.
dangerous-agent
An agent with security issues for testing.