code-testing-builder

code-testing-builder is an agent for Claude Code from dotnet/skills. It costs 37 tokens per session (905 once invoked), scanned A, original, MIT.

An agent that builds and compiles software projects in different programming languages, then reports whether they succeeded and what errors occurred.

In plain words
What is it for?
Use it to run the appropriate build command for .NET, JavaScript, Python, Go, Rust, or other supported project types and inspect compilation failures.
Why use it?
It gives you a direct build check when you need to know whether code compiles and which problems still prevent a successful build.

Agent for Claude Code

Written for Claude Code: user-invocable in frontmatter.

Part of the dotnet-test plugin — 24 skills, 10 agents shipped together

Good fit Use it to run the appropriate build command for .NET, JavaScript, Python, Go, Rust, or other supported project types and inspect compilation failures.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/dotnet/skills/code-testing-builder
About the project

.NET/skills is a repository of reusable instructions and custom agents that help AI coding agents work with .NET and C#. It supports tasks such as C# language-server integration, data access, diagnostics, builds, packages, upgrades, MAUI, templates, and AI development. The catalogue entries are the repository's skills, agents, plugins, and instructions.

dotnet/skills · 5,696 stars · on GitHub

Install

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.

Clone the repo
git clone --depth 1 https://github.com/dotnet/skills

Made for: Claude Code.

Or install dotnet-test, the plugin that ships this one along with the rest of its 24 skills, 10 agents.

Wrote 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.

agentmods badge for code-testing-builder

README.md
[![agentmods](https://agentmods.dev/badge/agents/dotnet/skills/code-testing-builder/github.svg)](https://agentmods.dev/agents/dotnet/skills/code-testing-builder)
Your own site
<a href="https://agentmods.dev/agents/dotnet/skills/code-testing-builder"><img src="https://agentmods.dev/badge/agents/dotnet/skills/code-testing-builder/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.

agentmods 80×15 button for code-testing-builder

Your own site · 80×15
<a href="https://agentmods.dev/agents/dotnet/skills/code-testing-builder"><img src="https://agentmods.dev/badge/agents/dotnet/skills/code-testing-builder.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 37 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 905 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00037 $0.00905
Opus 5.5 $0.00015 $0.00362
Sonnet 5.5 $0.00007 $0.00181
Haiku 4.5 $0.00004 $0.00090

Measured 12d ago against content hash 1632956f2461, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

code-testing-builder 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 12d 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.

plugins/dotnet-test/agents/code-testing-builder.agent.md · 105 lines

How it starts

The opening of the file, as written. The whole thing — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Builder Agent

You build/compile projects and report the results. You are polyglot — you work with any programming language.

Language-specific guidance: Use the caller-provided command and captured language guidance when available. Read the supplied or runtime-listed code-testing-extensions catalog and matching file only when build guidance is missing; the catalog is reference-only, not an invocable skill.

Your Mission

Run the appropriate build command once and report success or failure with the actionable diagnostics needed by the caller. Do not edit files or broaden the requested build scope.

Process

1. Discover Build Command

If not provided, check in order:

  1. The exact command or relevant Commands excerpt supplied by the caller; if the caller instead supplies a document, it must provide its absolute <TESTAGENT_DIR>/research.md or <TESTAGENT_DIR>/plan.md path
  2. Project files:
    • SDK-style *.csproj / *.sln → dotnet build
    • Classic non-SDK *.csproj / *.sln → repository-documented MSBuild command
    • package.json → npm run build or npm run compile
    • pyproject.toml / setup.py → python -m py_compile or skip
    • go.mod → go build ./...
    • Cargo.toml → cargo build
    • Makefile → make or make build

Stop discovery as soon as a repository-owned command is established. If several independent manifests must be inspected, read them in one batch where the available tools support it; do not repeat searches already answered by the caller or research document.

2. Run Build Command

For scoped builds (if specific files are mentioned):

  • SDK-style C#: dotnet build ProjectName.csproj
  • Classic non-SDK C#: use the command from research/scripts/CI (commonly MSBuild.exe ProjectName.csproj /t:Build); never migrate the project to make dotnet build work
  • TypeScript: npx tsc --noEmit
  • Go: go build ./...
  • Rust: cargo build

3. Parse Output

Look for error messages (CS\d+, TS\d+, E\d+, etc.), warning messages, and success indicators.

Read the full file on GitHub · 105 lines

Changes

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.

  1. 12d ago Changed · +1 lines 1632956f2461
  2. 26d ago Changed · +19 lines df4f5484650d
  3. 1mo ago Changed · +2 lines 28f061d54afd
  4. 1mo ago First seen · 83 lines · 37 tokens per session scan A ce8b48afc7b3

Subscribe to this mod's changes

code-testing-builder is an agent published in the GitHub repository dotnet/skills (5,696 stars, last pushed today), licensed MIT. It adds 37 tokens to every session and 905 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-09-03.

Related

Other agents, from other repositories

review-obsidian-guidelines

Reviews a diff of obsidian-reminder against Obsidian's community plugin guidelines and directory review rules that ESLint does not already enforce — manifest metadata, command naming, settings UI, styling, mobile compatibility, vault access APIs. Used by the pr-review workflow; read-only.

uphy/obsidian-reminder · 63 tokens

debugger

Diagnoses and fixes failed modules using root-cause analysis, not guessing.

TT-Wang/forge · 17 tokens

debugger

Investigate errors systematically to find root cause before attempting fixes. Gathers evidence, analyzes patterns, and forms testable hypotheses.

bostonaholic/rpikit · 28 tokens

loom-advisor

Read-only advisory agent for debugging and repeated failures. Spawned instead of a blind retry when an implementer has failed twice on the same task, or a bug resists straightforward diagnosis. Returns a root-cause diagnosis plus one concrete next step.

cosmix/loom · 53 tokens

evolve-retrospective

Failure post-mortem agent for the Evolve Loop. Fires only on Auditor FAIL or WARN verdicts. Reads cycle artifacts and produces a structured retrospective + failure-lesson YAML files. READ-ONLY outside the lessons directory.

mickeyyaya/evolve-loop · 51 tokens

runtime-observer

Dynamic observation agent designed to inspect running applications, trace state transitions, log API traffic, and flag race conditions, cache states, or timing issues. Trigger with "start runtime observer", "observe live system", "trace API calls", or during characterization test validation.

richfrem/agent-plugins-skills · 56 tokens