Getting it into your agent
There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.
Wrote 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/cyberbird2048/gbrainmcp-clean/testing)<a href="https://agentmods.dev/skills/cyberbird2048/gbrainmcp-clean/testing"><img src="https://agentmods.dev/badge/skills/cyberbird2048/gbrainmcp-clean/testing.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.00063 | $0.02034 |
| Opus 5 | $0.00032 | $0.01017 |
| Sonnet 5 | $0.00013 | $0.00407 |
| Haiku 4.5 | $0.00006 | $0.00203 |
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 5d 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
94% identical to testing — 4 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 — 257 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Testing Skill — Validation + Daily Health & Regression Intelligence
Convention: see conventions/quality.md for the test-before-bulk pattern; this skill enforces it across the project's own test suite.
Two modes
This skill has two related but distinct modes:
-
Skill conformance validation — gbrain's own conformance bar (the original 1.0 scope). Validates every skill has SKILL.md with frontmatter, every reference exists, manifest + resolver coverage round-trips.
-
Project test-suite health (v0.25.1 extension) — runs the project's tiered test suite and produces a regression-classified report. Used by daily cron, container-restart bootstrap, and "how are the tests" prompts.
Pick the mode by trigger.
Mode 1: Skill conformance validation
Contract
This mode guarantees:
- Every skill directory has a
SKILL.mdfile - Every
SKILL.mdhas valid YAML frontmatter (name,description) - Every
SKILL.mdhas required sections pertest/skills-conformance.test.ts skills/manifest.jsonlists every skill directoryskills/RESOLVER.mdreferences every skill in the manifestopenclaw.plugin.jsonskills[]round-trips with both- No MECE violations (duplicate triggers across skills)
Phases
- Walk skills directory. List all subdirs containing
SKILL.md. - Validate frontmatter. Parse YAML, check required fields.
- Validate sections. Check for the required headings.
- Check manifest. Every skill dir must be in
manifest.json. - Check resolver. Every manifest skill must have a RESOLVER row.
- Check round-trip. RESOLVER trigger ↔ frontmatter triggers.
- Report results.
Automation
bun test test/skills-conformance.test.ts test/resolver.test.ts
The CI-gated check is the package.json test script.
Output format
Skill Validation Report
========================
Skills found: N
Conformance: N/N pass
Manifest coverage: N/N
Resolver coverage: N/N
Round-trip: N/N
MECE violations: N
Issues:
- <skill>: <issue>
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.
- 5d ago First seen · 257 lines · 63 tokens per session scan A 6313e5db9b22
testing is a skill published in the GitHub repository cyberbird2048/gbrainmcp-clean (0 stars, last pushed 1mo ago), licensed MIT. It adds 63 tokens to every session and 2,034 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 94% identical to testing, differing in 4 lines, and is treated as a copy.
Other skills, from other repositories
migrate-xunit-to-xunit-v3
Migrate .NET test projects from xUnit.net v2 to xunit.v3 and fix v3 breaks. Use for package/CPM conversion, OutputType=Exe, preserving the VSTest or MTP runner (including projects currently using YTest.MTP.XUnit2), incompatible TFMs, async void tests, string-to-Type attributes, custom Fact/Theory/BeforeAfterTest…
nunit-testing
Use when writing or modifying tests in NUnit's own test projects, or when making a behavioral change to production code that needs test coverage. Covers test structure, attribute choice, helper visibility, platform guards, and which test projects are real.
go-testing
Trigger: Go tests, go test coverage, Bubbletea teatest, golden files. Apply focused Go testing patterns.
detect-flaky-tests
Detects flaky Go tests by analyzing GitHub Actions workflow runs across the last 7 days and all PRs — covering both the run-tests job (unit/integration) and the e2e-test job (gVisor and microVM lanes). For each newly-detected flaky test or infra issue, opens a GitHub issue with full evidence and a draft fix PR. Does…
add-go-test
Write or extend Go unit tests in this repo. Use when the user asks to add or update Go tests.
dart-test
DART Test: unit tests, integration tests, CI validation, and debugging.