Borrowing it
Nothing to install: this file belongs to Konnexx-Software-Developers/konnexx-dev-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/Konnexx-Software-Developers/konnexx-dev-mcp/main/.cursor/commands/test-fix-incremental.mdgit clone --depth 1 https://github.com/Konnexx-Software-Developers/konnexx-dev-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/commands/konnexx-software-developers/konnexx-dev-mcp/test-fix-incremental)<a href="https://agentmods.dev/commands/konnexx-software-developers/konnexx-dev-mcp/test-fix-incremental"><img src="https://agentmods.dev/badge/commands/konnexx-software-developers/konnexx-dev-mcp/test-fix-incremental/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/konnexx-software-developers/konnexx-dev-mcp/test-fix-incremental"><img src="https://agentmods.dev/badge/commands/konnexx-software-developers/konnexx-dev-mcp/test-fix-incremental.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.01102 |
| Opus 5 | $0.00000 | $0.00551 |
| Sonnet 5 | $0.00000 | $0.00220 |
| Haiku 4.5 | $0.00000 | $0.00110 |
Grade A, and why
test-fix-incremental 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 8d 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 — 145 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test Fix Incremental (Vitest)
Use this command for: Large test suites or when you want to fix tests one at a time
Test Framework: Vitest
Command: npm run test:run (always use this - npm test runs in watch mode and will hang)
You are a test automation assistant for the konnexx-dev-mcp package. Use this command to run tests incrementally - stopping at the first failure, fixing it, then continuing. This is ideal for large test suites after big refactors where running all tests at once is too slow.
Important: Git Command Usage
ALWAYS use git --no-pager prefix for all git commands to prevent pagination that blocks AI execution:
- ✅
git --no-pager diff(notgit diff) - ✅
git --no-pager diff --name-only(notgit diff --name-only) - ✅
git --no-pager status(notgit status)
Step 0: MCP-Enhanced Setup (Optional)
Before running tests, use MCPs for better context:
Use Filesystem MCP to Find Test Files
- Search for test files related to changed code using Filesystem MCP
- Look for patterns:
src/**/*.test.ts - This helps identify which tests might be affected
Use Context7 MCP for Testing Patterns (When Fixing)
- Query Vitest/TypeScript testing best practices when fixing tests
- Examples: "How do I mock modules in Vitest?", "TypeScript test assertion examples"
Step 1: Run Tests and Stop at First Failure
Execute in terminal:
npm run test:run
What happens:
- Vitest runs all tests
- Stops at first failure (or continues if using default behavior)
- Shows error for the failing test
Alternative - Run specific test file:
npm run test:run -- src/project-detection.test.ts
Step 2: Identify First Failure
Review the test output:
- Which test failed? (test file and test name)
- What's the error? (error message, stack trace)
- What file is being tested? (source file)
Example failure:
FAIL src/project-detection.test.ts > Project Detection > should detect Laravel API project
AssertionError: expected 'unknown' to be 'api'
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.
- 8d ago First seen · 145 lines · 0 tokens per session scan A 093ad5171600
test-fix-incremental is a command published in the GitHub repository Konnexx-Software-Developers/konnexx-dev-mcp (0 stars, last pushed 7mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,102 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
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.
lg:node
Create, modify, and manage nodes in LangGraph graphs including LLM nodes, tool nodes, human-in-the-loop, subgraphs, and conditional nodes.
test
Execute a comprehensive test run for the following target.
frappe-test
Run unit and integration tests for Frappe apps with coverage reports.
implement-fix
Minimal pipeline for test-fixing tasks.