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.
npx agentmods add skills/fpindej/netrock/add-testnpx skills add fpindej/netrock --skill add-testgit clone --depth 1 https://github.com/fpindej/netrockWrote 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/fpindej/netrock/add-test)<a href="https://agentmods.dev/skills/fpindej/netrock/add-test"><img src="https://agentmods.dev/badge/skills/fpindej/netrock/add-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 | $0.00006 | $0.01015 |
| Opus 5 | $0.00003 | $0.00508 |
| Sonnet 5 | $0.00001 | $0.00203 |
| Haiku 4.5 | $0.00001 | $0.00102 |
Grade A, and why
add-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 4d 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.
How it starts
The opening of the file, as written. The whole thing — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Adds tests. Specify test type or infer from context.
Unit Test
For pure logic in Shared, Domain, or Application layers.
- Create
src/backend/tests/MyProject.Unit.Tests/{Layer}/{ClassUnderTest}Tests.cs - Structure:
{Method}_{Scenario}_{Expected}naming - No mocking, no DI - test pure inputs and outputs
- Verify:
dotnet test src/backend/tests/MyProject.Unit.Tests -c Release
Component Test
For service business logic with mocked dependencies.
- Create
src/backend/tests/MyProject.Component.Tests/Services/{Service}Tests.cs - Create mocks in constructor:
private readonly MyProjectDbContext _dbContext = TestDbContextFactory.Create(); private readonly IOrderRepository _orderRepo = Substitute.For<IOrderRepository>(); private readonly HybridCache _cache = Substitute.For<HybridCache>(); - For Identity:
IdentityMockHelpers.CreateMockUserManager()/CreateMockRoleManager() - Assert on
Result:Assert.True(result.IsSuccess); Assert.Equal(expectedId, result.Value); - Verify:
dotnet test src/backend/tests/MyProject.Component.Tests -c Release
API Integration Test
For testing the full HTTP pipeline (routes, auth, validation, status codes).
- Create
src/backend/tests/MyProject.Api.Tests/Controllers/{Controller}Tests.cs - Structure:
public class OrdersControllerTests : IClassFixture<CustomWebApplicationFactory>, IDisposable { private readonly CustomWebApplicationFactory _factory; private readonly HttpClient _client; public OrdersControllerTests(CustomWebApplicationFactory factory) { _factory = factory; _client = factory.CreateClient(); } public void Dispose() => _client.Dispose(); } - Auth per-request via
Authorizationheader:"Test"- basic authenticated userTestAuth.WithPermissions(AppPermissions.Users.View)- specific permissionsTestAuth.Superuser()- bypasses all checks- No header - unauthenticated (401)
- Configure mock returns:
_factory.AdminService.Method(...).Returns(...); - If service interface not mocked in
CustomWebApplicationFactory, add it there first - For 200/201 responses, add response contract assertions using frozen records in
Contracts/ResponseContracts.cs - Verify:
dotnet test src/backend/tests/MyProject.Api.Tests -c Release
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.
- 4d ago First seen · 114 lines · 6 tokens per session scan A 0f4305ce7bde
add-test is a skill published in the GitHub repository fpindej/netrock (231 stars, last pushed 5d ago), licensed MIT. It adds 6 tokens to every session and 1,015 once invoked, about $0.0000 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-30.
Other skills, from other repositories
api-design
Guidelines for RESTful API design, endpoint naming conventions, and standardizing JSON responses.
python
Enforces FastAPI, Dependency Injection, and general Python coding standards based on the repository structure.
python-testing
Guidelines for Python testing using pytest and pytest-asyncio. Use when writing or debugging backend tests.
react
Guidelines for the React frontend, TanStack ecosystem, and React 19 standards. Use when modifying the UI.
react-testing
Frontend testing standards using Vitest, React Testing Library, and Playwright. Use when writing UI tests.
documentation
Standards for code documentation, docstrings, and maintaining README files.