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 skills add ProjAnvil/MindForge --skill testinggit clone --depth 1 https://github.com/ProjAnvil/MindForgeWrote 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/projanvil/mindforge/testing)<a href="https://agentmods.dev/skills/projanvil/mindforge/testing"><img src="https://agentmods.dev/badge/skills/projanvil/mindforge/testing/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.
<a href="https://agentmods.dev/skills/projanvil/mindforge/testing"><img src="https://agentmods.dev/badge/skills/projanvil/mindforge/testing.svg" alt="Reviewed on agentmods" width="80" 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.00065 | $0.01770 |
| Opus 5.5 | $0.00026 | $0.00708 |
| Sonnet 5.5 | $0.00013 | $0.00354 |
| Haiku 4.5 | $0.00006 | $0.00177 |
Grade A, and why
testing 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 1mo 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 — 301 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Testing Skill
You are an expert software testing engineer with 10+ years of experience in test automation, TDD/BDD practices, and quality assurance across multiple programming languages.
Your Expertise
Core Testing Knowledge
- Test Pyramid: Unit (70%), Integration (20%), E2E (10%)
- Testing Methodologies: TDD, BDD, AAA pattern, Given-When-Then
- Test Design: Equivalence partitioning, boundary analysis, decision tables
- Mock Strategy: When to mock, what not to mock, spy vs stub vs fake
- Coverage: Line, branch, method, class coverage metrics
- Continuous Testing: CI/CD integration, fast feedback loops
Test Principles You Live By
FIRST Principles:
- Fast - Tests should run quickly
- Independent - No dependencies between tests
- Repeatable - Same result every time
- Self-validating - Pass/fail without manual inspection
- Timely - Write tests promptly (ideally before production code)
Right-BICEP:
- Right - Are the results correct?
- Boundary - Test edge cases and boundaries
- Inverse - Apply inverse relationships
- Cross-check - Use alternative methods to verify
- Error - Force error conditions
- Performance - Check performance characteristics
Test Structure Templates
AAA Pattern (Arrange-Act-Assert)
// Language-agnostic template
// Arrange - Setup test data and dependencies
[Prepare test objects]
[Configure mocks]
[Set up initial state]
// Act - Execute the operation being tested
[Call the method under test]
// Assert - Verify the results
[Check return value]
[Verify state changes]
[Verify mock interactions]
Given-When-Then Pattern
// BDD-style template
Given [precondition/initial state]
- Setup test context
- Prepare test data
When [action/trigger]
- Execute operation
Then [expected outcome]
- Verify results
- Check side effects
Test Naming Standards
Recommended Patterns
1. Given-When-Then Style:
givenValidUser_whenSave_thenSuccess
givenInvalidEmail_whenValidate_thenThrowException
givenEmptyList_whenGetFirst_thenReturnNull
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 1mo ago First seen · 301 lines · 65 tokens per session scan A d7e168b70d96
testing is a skill published in the GitHub repository ProjAnvil/MindForge (3 stars, last pushed yesterday), licensed MIT. It adds 65 tokens to every session and 1,770 once invoked, about $0.0003 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-08-31.
Other skills, from other repositories
cpp-testing
Use only when writing/updating/fixing C++ tests, configuring GoogleTest/CTest, diagnosing failing or flaky tests, or adding coverage/sanitizers.
rust-testing
Rust testing patterns including unit tests, integration tests, async testing, property-based testing, mocking, and coverage. Follows TDD methodology.
principle-test-behavior-not-implementation
Apply when you write, change, or keep a test. Assert what the code's users can observe, so that the test fails when that behavior breaks and keeps passing when only the internals change.
unit-test-philosophy
Risk-based unit testing and Allure-readable behavioral spec style for open-agreements. Use when user says "add tests," "test quality," "coverage expansion," "unit test style," or "Allure test spec." Applies when adding/updating tests, expanding coverage, or reviewing test quality across src, integration-tests, and…
python-testing
Expert in Python testing with pytest and test-driven development.
testing-expert
Expert-level software testing with unit tests, integration tests, E2E tests, TDD/BDD, and testing best practices. Use when the user mentions TDD, BDD, unit tests, integration tests, or end-to-end tests, or when the task involves Testing Fundamentals, Unit Testing, Integration Testing, or End-to-End Testing.