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 noerd-dev/noerd --skill noerd-testinggit clone --depth 1 https://github.com/noerd-dev/noerdWrote 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/noerd-dev/noerd/noerd-testing)<a href="https://agentmods.dev/skills/noerd-dev/noerd/noerd-testing"><img src="https://agentmods.dev/badge/skills/noerd-dev/noerd/noerd-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/noerd-dev/noerd/noerd-testing"><img src="https://agentmods.dev/badge/skills/noerd-dev/noerd/noerd-testing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00121 | $0.01453 |
| Opus 5.5 | $0.00048 | $0.00581 |
| Sonnet 5.5 | $0.00024 | $0.00291 |
| Haiku 4.5 | $0.00012 | $0.00145 |
Grade A, and why
noerd-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 — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Testing with Noerd
Tests are Pest tests that live inside the module (app-modules/{module}/tests/), never in the
host project. Hard rules: noerd/noerd Boost guideline ("Tests Must Test Functionality, Not
Current Configuration", "Testing YAML-Driven Detail Forms"). Docs: vendor/noerd/noerd/docs/testing.md.
1. The one rule that breaks most tests
YAML under app-configs/ is per-installation configuration. A test that asserts its current
content is wrong by definition:
- ✗
assertSeeHtml('data-theme="compact"')against a real detail, exact tab/column/field lists, titles, which field is required, whether a list opens its detail by route or by component. - ✓ Prove the EFFECT of a configuration with synthetic layouts, runtime-written fixture YAMLs, factories and runtime-registered routes.
- ✓ Architecture guardrails are fine (a detail YAML has no
widgets:/relations:; a page blade embeds thedetail:its YAML names).
2. Global helpers (tests/helpers.php in the noerd package)
Not composer-autoloaded (test code must never load in production). Suites binding
Noerd\Tests\TestCase get them for free; every other tests/Pest.php loads them once with
\Noerd\Tests\HelperLoader::load(); — never a hard-coded path, never a root composer.json entry.
| Helper | Use |
|---|---|
validDetailPayload(Model::class, $overrides) |
complete factory-sourced detailData for store-success tests |
requiredLayoutFields($component) |
required field names from the live pageLayout for validation tests |
registerTestLivewireRoute($uri, $component, $name) |
register a named Route::livewire() inside a test (route-vs-component mechanics) |
assertModuleDependenciesDeclared($moduleDir, $allowedPackages = []) |
module-independence guard: fails when another module's namespace appears without a require entry |
assertModuleUpdateCommandPublishesConfigs($command, $moduleDir, $moduleKey) |
the standard proof for a noerd:update-{module} command |
zzNormalizeSpaces($value) |
collapse ICU's U+00A0 / U+202F spaces to plain ones before asserting a formatted value |
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 Changed · +4 lines d729c6db5800
- 1mo ago Changed · +15 lines 28fe5314efd0
- 1mo ago First seen · 79 lines · 121 tokens per session scan A 4a2d4cdb75f6
noerd-testing is a skill published in the GitHub repository noerd-dev/noerd (17 stars, last pushed 5d ago), licensed MIT. It adds 121 tokens to every session and 1,453 once invoked, about $0.0005 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-30.
Other skills, from other repositories
Codeception Testing
Expert-level Codeception testing skill for PHP applications. Covers acceptance, functional, and unit testing with the Actor pattern, BDD-style syntax, Page Objects, API testing, and database helpers.
craft-pest
Testing Craft CMS 5 plugins and modules with Pest — test isolation, database safety, and the markhuot/craft-pest-core harness. ALWAYS load when writing, running, fixing, or reviewing tests for a Craft plugin or module, and whenever a suite touches a real Craft install. Covers why rollback is opt-in, tests/Pest.php +…
phpunit-unit-test-reviewing
Internal sub-skill. Do not auto-activate. Use only when explicitly invoked by name by another skill or agent.
phpunit-unit-test-writing
Use this skill when the user asks to write, generate, create, or add PHPUnit unit tests for a Shopware 6 source class — phrases like "write unit tests for X", "generate tests for ClassName", "create PHPUnit tests", "add test coverage", "test this class", "cover this with tests", "I need tests for", "unit test this"…
php-testing
Use when writing/configuring tests on a non-Laravel PHP project — PHPUnit vs Pest. Do NOT use for Laravel test helpers or quality tooling (php-quality-tooling).
laravel-testing
Laravel 13 testing with Pest PHP 4 or PHPUnit 12. Use when writing feature tests, unit tests, or any test code in a Laravel application. Triggers on tasks involving HTTP tests, model factories, database assertions, mocking facades, authentication testing, or test organisation patterns.