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.
git clone --depth 1 https://github.com/srnichols/plan-forgeWrote 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/srnichols/plan-forge/new-test)<a href="https://agentmods.dev/commands/srnichols/plan-forge/new-test"><img src="https://agentmods.dev/badge/commands/srnichols/plan-forge/new-test.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.00024 | $0.00558 |
| Opus 5 | $0.00012 | $0.00279 |
| Sonnet 5 | $0.00005 | $0.00112 |
| Haiku 4.5 | $0.00002 | $0.00056 |
Grade A, and why
new-test 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 today.
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 — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create New Test
Scaffold test classes following project conventions.
Test Naming Convention
{MethodUnderTest}_When{Condition}_Should{ExpectedBehavior}
Examples:
CreateProduct_WhenNameIsNull_ShouldThrowValidationExceptionGetById_WhenNotFound_ShouldReturnNullCalculateTotal_WhenDiscountApplied_ShouldReturnReducedPrice
Unit Test Pattern
public class {ClassName}Tests
{
private readonly Mock<I{Dependency}> _mockDependency;
private readonly {ClassUnderTest} _sut; // System Under Test
public {ClassName}Tests()
{
_mockDependency = new Mock<I{Dependency}>();
_sut = new {ClassUnderTest}(_mockDependency.Object, NullLogger<{ClassUnderTest}>.Instance);
}
[Fact]
[Trait("Category", "Unit")]
public async Task Method_WhenCondition_ShouldExpected()
{
// Arrange
_mockDependency
.Setup(x => x.GetAsync(It.IsAny<Guid>(), It.IsAny<CancellationToken>()))
.ReturnsAsync(new EntityDto { Id = Guid.NewGuid() });
// Act
var result = await _sut.MethodAsync(Guid.NewGuid(), CancellationToken.None);
// Assert
result.Should().NotBeNull();
}
}
Integration Test Pattern (Testcontainers)
public class {ClassName}IntegrationTests : IAsyncLifetime
{
private readonly PostgreSqlContainer _postgres = new PostgreSqlBuilder()
.WithImage("postgres:16-alpine")
.Build();
public async Task InitializeAsync() => await _postgres.StartAsync();
public async Task DisposeAsync() => await _postgres.DisposeAsync();
[Fact]
[Trait("Category", "Integration")]
public async Task Repository_WhenInserted_ShouldBeRetrievable()
{
// Arrange — real DB connection
// Act — actual repository call
// Assert — verify round-trip
}
}
Trait Categories
| Trait | When to Use |
|---|---|
[Trait("Category", "Unit")] |
Pure unit tests with mocks |
[Trait("Category", "Integration")] |
Tests hitting real DB |
[Trait("Category", "Smoke")] |
Fast subset for PR validation |
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.
- today First seen · 88 lines · 24 tokens per session scan A 3e3af920fd96
new-test is a command published in the GitHub repository srnichols/plan-forge (5 stars, last pushed today), licensed MIT. It adds 24 tokens to every session and 558 once invoked, about $0.0001 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-09-08.
Other commands, from other repositories
coding-flow
Light coding workflow: features, fixes, refactors, unit tests, etc.; scales small to large.
modernization-flow-testing
Phase 3 Testing (optional) of modernization-flow.
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.
checklist
Generate a custom checklist for the current feature based on user requirements.