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.
curl -O https://raw.githubusercontent.com/solanabr/solana-vault-standard/main/.claude/commands/test-dotnet.mdgit clone --depth 1 https://github.com/solanabr/solana-vault-standardWrote 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/solanabr/solana-vault-standard/test-dotnet)<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>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.00012 | $0.03643 |
| Opus 5 | $0.00006 | $0.01821 |
| Sonnet 5 | $0.00002 | $0.00729 |
| Haiku 4.5 | $0.00001 | $0.00364 |
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.
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.
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.
Related Skills
- unity.md - Unity patterns and testing
- playsolana.md - PlaySolana specifics
TDD Workflow (6 Phases)
When developing with TDD, follow these phases strictly:
Phase 1: RED - Write Failing Test
- Create test file in appropriate location (
Tests/EditMode/orTests/PlayMode/) - Write minimal test that fails for the right reason
- Run test to confirm it fails
- 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
- Write minimal production code to pass the test
- Only write enough code to pass - no more
- Run test to confirm it passes
- Commit if green
public class Calculator
{
public int Calculate(int a, int b) => a + b; // Minimal implementation
}
Phase 3: REFACTOR - Clean Up
- Improve code structure without changing behavior
- Run tests after each refactoring step
- Keep tests green throughout
- Apply SOLID principles, remove duplication
Phase 4: Iterate
- Return to Phase 1 for next test case
- Build up functionality incrementally
- Each cycle: RED → GREEN → REFACTOR
Phase 5: Integration
- After unit tests pass, run integration tests
- Test component interactions
- For Unity: run Play Mode tests
Phase 6: Review
- Review test coverage
- Check for missing edge cases
- Ensure tests are maintainable
- Remove any redundant tests
Core Workflow: Build → Respond → Iterate
Operate in fast, surgical development cycles with minimal token usage.
Execution Flow
- Understand the Request: Analyze minimum code required
- Make the Change: Implement surgical edit
- Build:
dotnet build --no-restore --nologo --verbosity minimal - If Build Fails: Retry once if obvious fix, then STOP and ask
- Run Tests:
dotnet test --no-build --nologo --verbosity minimal - If Tests Fail: Extract failures with
rg, fix if obvious, else STOP and ask
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 · 643 lines · 12 tokens per session scan A 14ccbfa20c51
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.
Other commands, from other repositories
dotnet-skills
List the .NET skills, subagents, and lifecycle commands shipped by this plugin (adapted from addyosmani/agent-skills — spec-driven development, TDD, code review, security audit, test engineering, and more with .NET 8+, C# 12+, xUnit/MSTest, EF Core, Avalonia framing).
build
Implement tasks incrementally in .NET — RED/GREEN/REFACTOR, dotnet build, dotnet test, commit. Add "auto" to run the whole plan in one approved pass.
test
Run .NET TDD workflow — write failing xUnit/MSTest tests, implement, verify. For bugs, use the Prove-It pattern.
cpp-test
Enforce TDD workflow for C++. Write GoogleTest tests first, then implement. Verify coverage with gcov/lcov.
test-dotnet
Run .NET/C# tests for Unity projects and backend services.
rust-test
Enforce TDD workflow for Rust. Write tests first, then implement. Verify 80%+ coverage with cargo-llvm-cov.