solana-vault-standard: Command for Claude Code

.claude/commands/test-dotnet.md

test-dotnet is a command for Claude Code from solanabr/solana-vault-standard. It costs 12 tokens per session (3,643 once invoked), scanned A, a copy of test-dotnet, MIT.

A test-running command for Unity games and ordinary .NET or C# services. It supports TDD, a method where you write a failing test first, make it pass with the smallest change, and then clean up the code.

In plain words
What is it for?
Use it to run Unity Edit Mode and Play Mode tests or standard .NET tests. It helps build features through failing tests, passing implementations, refactoring, and repeated checks.
Why use it?
It gives a fixed workflow for checking behavior before and after code changes. This helps catch regressions while developing Unity projects or backend services.

Command for Claude Code

Written for Claude Code: installed under .claude/.

This is solanabr/solana-vault-standard's own configuration. It tells Claude Code how to work on solana-vault-standard itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything solana-vault-standard configures →

Reuse

Borrowing it

Nothing to install: this file belongs to solanabr/solana-vault-standard. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/solanabr/solana-vault-standard/main/.claude/commands/test-dotnet.md
Clone the repo
git clone --depth 1 https://github.com/solanabr/solana-vault-standard

Made for: Claude Code.

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 test-dotnet

README.md
[![agentmods](https://agentmods.dev/badge/commands/solanabr/solana-vault-standard/test-dotnet.svg)](https://agentmods.dev/commands/solanabr/solana-vault-standard/test-dotnet)
Your own site
<a href="https://agentmods.dev/commands/solanabr/solana-vault-standard/test-dotnet"><img src="https://agentmods.dev/badge/commands/solanabr/solana-vault-standard/test-dotnet.svg" alt="Measured on agentmods" height="20"></a>
Per session 12 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 3,643 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 95% copy Near-identical to another mod 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.00012 $0.03643
Opus 5 $0.00006 $0.01821
Sonnet 5 $0.00002 $0.00729
Haiku 4.5 $0.00001 $0.00364

Measured 8d ago against content hash 14ccbfa20c51, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

test-dotnet 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.

Origin

This is a copy

95% identical to test-dotnet — 3 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.claude/commands/test-dotnet.md · 643 lines

How it starts

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

You are running .NET/C# tests. This command covers Unity Test Framework (Edit Mode and Play Mode) and standard .NET testing.


TDD Workflow (6 Phases)

When developing with TDD, follow these phases strictly:

Phase 1: RED - Write Failing Test

  1. Create test file in appropriate location (Tests/EditMode/ or Tests/PlayMode/)
  2. Write minimal test that fails for the right reason
  3. Run test to confirm it fails
  4. Do NOT write production code yet
[Test]
public void Calculate_WithValidInput_ReturnsExpected()
{
    var sut = new Calculator();  // Class doesn't exist yet

    var actual = sut.Calculate(10, 2);

    Assert.That(actual, Is.EqualTo(12));
}

Phase 2: GREEN - Make Test Pass

  1. Write minimal production code to pass the test
  2. Only write enough code to pass - no more
  3. Run test to confirm it passes
  4. Commit if green
public class Calculator
{
    public int Calculate(int a, int b) => a + b;  // Minimal implementation
}

Phase 3: REFACTOR - Clean Up

  1. Improve code structure without changing behavior
  2. Run tests after each refactoring step
  3. Keep tests green throughout
  4. Apply SOLID principles, remove duplication

Phase 4: Iterate

  1. Return to Phase 1 for next test case
  2. Build up functionality incrementally
  3. Each cycle: RED → GREEN → REFACTOR

Phase 5: Integration

  1. After unit tests pass, run integration tests
  2. Test component interactions
  3. For Unity: run Play Mode tests

Phase 6: Review

  1. Review test coverage
  2. Check for missing edge cases
  3. Ensure tests are maintainable
  4. Remove any redundant tests

Core Workflow: Build → Respond → Iterate

Operate in fast, surgical development cycles with minimal token usage.

Execution Flow

  1. Understand the Request: Analyze minimum code required
  2. Make the Change: Implement surgical edit
  3. Build: dotnet build --no-restore --nologo --verbosity minimal
  4. If Build Fails: Retry once if obvious fix, then STOP and ask
  5. Run Tests: dotnet test --no-build --nologo --verbosity minimal
  6. If Tests Fail: Extract failures with rg, fix if obvious, else STOP and ask

Read the full file on GitHub · 643 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. 8d ago First seen · 643 lines · 12 tokens per session scan A 14ccbfa20c51

Subscribe to this mod's changes

test-dotnet is a command published in the GitHub repository solanabr/solana-vault-standard (23 stars, last pushed 5mo ago), licensed MIT. It adds 12 tokens to every session and 3,643 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 95% identical to test-dotnet, differing in 3 lines, and is treated as a copy.