Borrowing it
Nothing to install: this file belongs to semihkayan/codeweave-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/semihkayan/codeweave-mcp/main/.claude/skills/test-harness/SKILL.mdgit clone --depth 1 https://github.com/semihkayan/codeweave-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/skills/semihkayan/codeweave-mcp/test-harness)<a href="https://agentmods.dev/skills/semihkayan/codeweave-mcp/test-harness"><img src="https://agentmods.dev/badge/skills/semihkayan/codeweave-mcp/test-harness.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.00057 | $0.00579 |
| Opus 5 | $0.00028 | $0.00290 |
| Sonnet 5 | $0.00011 | $0.00116 |
| Haiku 4.5 | $0.00006 | $0.00058 |
Grade A, and why
test-harness 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 7d 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
codeweave-mcp Test Harness
TestHarness in src/test-harness.ts. Write a temp .ts file and run with npx tsx <file> from the project root.
Modes
import { TestHarness } from "./src/test-harness.js";
const h = await TestHarness.setup("/absolute/path/to/project");
// All built-in tests (covers the 3 retained tools)
await h.testAll();
// Single tool
await h.test("semantic_search");
// Custom assertions
await h.run([
{
tool: "semantic_search",
args: { query: "user authentication", top_k: 5 },
label: "search: auth",
assert: d => d?.results?.length > 0 || "no results",
},
]);
// Manual call — returns parsed JSON
const data = await h.call("get_index_status", { workspace: "wordbox-api" });
await h.close(); // always close
Tool params & response shapes
semantic_search
Params: query (string, required), workspace?, scope?, top_k? (default 10), tags_filter? (string[]), side_effects_filter? (string[])
Response: { results, total_indexed, search_mode, warning? }
Each result: { function, file, module, signature, summary, tags, score, line_start, line_end, workspace? }
reindex
Params: workspace?, files? (string[]), force? (default false)
Response: { workspace?, status, mode, ast_index: { files, functions, classes }, embedded, vector_store_rows, elapsed_ms }
get_index_status
Params: workspace?
Single: { status, workspace, ast_index, vector_store, call_graph, type_graph, embedding_available, docstring_coverage, languages }
Multi: { status, workspaces[], embedding_available, model }
assert
Receives parsed JSON response. Return true = pass, string = fail reason.
Multi-workspace
Pass workspace as the short name (not full path): { workspace: "wordbox-api" }
Notes
setup()loads from cache — fast after first run.testAll()includes a force-full reindex at the end — slow on large projects.
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.
- 7d ago First seen · 71 lines · 57 tokens per session scan A e01d01fbd1b0
test-harness is a skill published in the GitHub repository semihkayan/codeweave-mcp (4 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 57 tokens to every session and 579 once invoked, about $0.0003 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 skills, from other repositories
mastermind-test-audit
Read-only review of whether the tests in a finished change actually prove its behaviour — changed code no test reaches, a test exercising a different path than the one that changed, an assertion edited to match the new output, and a suite that ran nothing. Use after implementation, and whenever a change claims to be…
mastermind-browser-verification
Turn "I opened it and it looks fine" into recorded evidence — accessibility tree over screenshot, console and network errors as mechanical failures, viewport and colour-scheme checks as a checklist, and anything unchecked marked unchecked. Use after implementing a UI change in a client that can drive a browser.
mastermind-test-impact
Build a focused, evidence-backed test plan from mastermind impact or mmcgtestimpact. Use when deciding which tests to run for a change, explaining direct/transitive/heuristic candidates, or sequencing fast feedback before the repository's required full test gate.
nexus-mapper
Generate a persistent .nexus-map/ knowledge base that lets any AI session instantly understand a codebase's architecture, systems, dependencies, and change hotspots. Use when starting work on an unfamiliar repository, onboarding with AI-assisted context, preparing for a major refactoring initiative, or enabling…
nexus-query
Precise, instant code structure queries for active development — answer 'who depends on this interface before I refactor it', 'how many modules break if I change this', 'what is the real impact radius of this feature change', 'which module is the true high-coupling hotspot in this legacy codebase'. Essential before…
codehelper-browser
When to use.