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.
npx agentmods add instructions/marcelkurvers/local-testing-agent/claude-mdgit clone --depth 1 https://github.com/marcelkurvers/local-testing-agentWrote 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/instructions/marcelkurvers/local-testing-agent/claude-md)<a href="https://agentmods.dev/instructions/marcelkurvers/local-testing-agent/claude-md"><img src="https://agentmods.dev/badge/instructions/marcelkurvers/local-testing-agent/claude-md.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 | $0.02058 | $0.02058 |
| Opus 5 | $0.01029 | $0.01029 |
| Sonnet 5 | $0.00412 | $0.00412 |
| Haiku 4.5 | $0.00206 | $0.00206 |
Grade A, and why
local-testing-agent CLAUDE.md 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 — 243 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
Overview
This is a local testing agent MCP server that automates test discovery, generation, and execution for multi-language projects. The project provides MCP tools for Claude to scan repositories, generate unit tests, run test suites, and produce coverage reports.
Supported Languages: Python, JavaScript/TypeScript, Go, Rust, Java, Ruby Test Coverage: 91% (120 tests passing) Quality: Production-ready with comprehensive test suite
Architecture
Two Main Entry Points
-
testing_agent.py - Phase 2 MCP server (latest version)
- Provides four MCP tools:
scan_repository,run_all_tests,run_all_tests_parallel,full_phase2_pipeline - New in Session 4: Parallel test execution with configurable concurrency
- Detects source and test files for 6 languages:
- Python:
*.pyfiles, pytest framework - JavaScript/TypeScript:
*.js,*.jsx,*.ts,*.tsxfiles, jest framework - Go:
*.gofiles,go testframework - Rust:
*.rsfiles,cargo testframework - Java:
*.javafiles, Maven/Gradle test frameworks - Ruby:
*.rbfiles, RSpec/Minitest frameworks
- Python:
- Generates AI test plans and coverage maps
- Runs language-specific test suites automatically
- Outputs:
.mcp_scan_snapshot.json,.mcp_test_report.json,TEST_COVERAGE_MAP.md,TEST_PLAN_AI.md
- Provides four MCP tools:
-
testing_engine/ - Phase 1 implementation (older version)
- Python package with modular components
file_scanner.py: Discovers Python source files, excluding venvs and cache dirsunit_test_generator.py: Auto-generates pytest stubs by parsing AST for public functions/methodspipeline.py: Orchestrates scanning → generation → pytest execution with coverage- Outputs to
.mcp/test_output.log
Key Differences
- Phase 2 (testing_agent.py): Multi-language support (6 languages), language-specific test framework execution, structured JSON reports, comprehensive detection patterns
- Phase 1 (testing_engine/): Python-only, always generates tests, simpler pipeline
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 First seen · 243 lines · 2,058 tokens per session scan A 4ad0c609a3d7
local-testing-agent CLAUDE.md is an instructions file published in the GitHub repository marcelkurvers/local-testing-agent (0 stars, last pushed 8mo ago), licensed MIT. It adds 2,058 tokens to every session, about $0.0103 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 instructions, from other repositories
Sighthound AGENTS.md
Instructions for Corgea/Sighthound, covering claude, commands, python / django test naming and agent skill.
glyph CLAUDE.md
Instructions for benmyles/glyph, covering claude.md, project overview, installation, macos and architecture.
appwrite AGENTS.md
AGENTS.md instructions for appwrite/appwrite, covering appwrite, commands, stack, layout and libraries.
joint CLAUDE.md
Claude Code instructions for clientIO/joint, covering claude.md, project overview, common commands, install dependencies and build distribution files (runs grunt).
azure-sdk-for-go go-code.instructions.md
Instructions for Azure/azure-sdk-for-go: All code should follow the guidelines from the Azure Go SDK Guidelines. This document is a summary of the most important guidelines to follow when contributing to the Azure Go SDK.
ai AGENTS.md
AGENTS.md instructions for vercel/ai, covering agents.md, project overview, repository structure, key directories and core package dependencies.