testing

testing is a skill for Claude Code from garrytan/gbrain. It costs 63 tokens per session (2,208 once invoked), scanned A, original, MIT.

A validation and test-health framework for agent skills and their project. It checks skill files and runs tests in stages, including unit tests, evaluations, integration tests, and system-health checks.

In plain words
What is it for?
Checking front matter, manifests, resolver entries, and test-suite health, including recurring daily reports.
Why use it?
It shows whether skills meet the project’s required structure and helps classify failures as regressions or other problems.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: mentions CLAUDE.md; mentions AGENTS.md; built for gbrain.

Needs its repository: it reads a path above its own folder, which exists only inside the repository. The line is **Convention:** see [conventions/quality.md](../conventions/quality.md) for.

Part of the gbrain plugin — 45 skills, 2 plugins shipped together

Good fit Checking front matter, manifests, resolver entries, and test-suite health, including recurring daily reports.

Compare 6 skills from other repositories ↓
About the project

GBrain is a memory and retrieval layer for AI agents that searches, connects, and synthesizes information from stored sources. It is used to give coding agents and autonomous agents access to knowledge beyond their current code, including shared company information with access controls. The catalogue add-ons help agents operate GBrain and connect it to agent workflows.

garrytan/gbrain · 31,066 stars · on GitHub

Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo
git clone --depth 1 https://github.com/garrytan/gbrain
agentmods
npx agentmods add skills/garrytan/gbrain/testing

Made for: Claude Code.

Or install gbrain, the plugin that ships this one along with the rest of its 45 skills, 2 plugins.

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.

agentmods badge for testing

README.md
[![agentmods](https://agentmods.dev/badge/skills/garrytan/gbrain/testing/github.svg)](https://agentmods.dev/skills/garrytan/gbrain/testing)
Your own site
<a href="https://agentmods.dev/skills/garrytan/gbrain/testing"><img src="https://agentmods.dev/badge/skills/garrytan/gbrain/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.

agentmods 80×15 button for testing

Your own site · 80×15
<a href="https://agentmods.dev/skills/garrytan/gbrain/testing"><img src="https://agentmods.dev/badge/skills/garrytan/gbrain/testing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 63 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,208 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • Snyk pass 7 Sept 2026
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00063 $0.02208
Opus 5.5 $0.00025 $0.00883
Sonnet 5.5 $0.00013 $0.00442
Haiku 4.5 $0.00006 $0.00221

Measured 14d ago against content hash c69fe3456aa9, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 14d 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.

Origin

Copies of this mod

2 near-identical copies found in the catalogue:

  • testing — 100% identical, 8 lines differ
  • testing — 94% identical, 12 lines differ
skills/testing/SKILL.md · 267 lines

How it starts

The opening of the file, as written. The whole thing — 267 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:

  1. 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.

  2. 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.md file
  • Every SKILL.md has valid YAML frontmatter (name, description)
  • Every SKILL.md has required sections per test/skills-conformance.test.ts
  • skills/manifest.json lists every skill directory
  • skills/RESOLVER.md references every skill in the manifest
  • openclaw.plugin.json skills[] round-trips with both
  • openclaw.plugin.json keeps OpenClaw install-required native plugin fields (id, object configSchema, and contracts.contextEngines when applicable)
  • No MECE violations (duplicate triggers across skills)

Phases

  1. Walk skills directory. List all subdirs containing SKILL.md.
  2. Validate frontmatter. Parse YAML, check required fields.
  3. Validate sections. Check for the required headings.
  4. Check manifest. Every skill dir must be in manifest.json.
  5. Check resolver. Every manifest skill must have a RESOLVER row.
  6. Check round-trip. RESOLVER trigger ↔ frontmatter triggers.
  7. Report results.

Automation

bun test test/skills-conformance.test.ts test/resolver.test.ts test/openclaw-plugin-manifest.test.ts

Read the full file on GitHub · 267 lines

Changes

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.

  1. 14d ago Changed c69fe3456aa9
  2. 17d ago Changed · +8 lines fdf7d9c2d9de
  3. 1mo ago First seen · 259 lines · 63 tokens per session scan A f1846ba7c350

Subscribe to this mod's changes

testing is a skill published in the GitHub repository garrytan/gbrain (31,066 stars, last pushed today), licensed MIT. It adds 63 tokens to every session and 2,208 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-09-03.

Related

Other skills, from other repositories

verify

Verify that a change really works before you claim completion.

Yeachan-Heo/oh-my-claudecode · 12 tokens

detect-static-dependencies

ACTIVATION PREREQUISITE: the request or discovered target must explicitly identify C#, .NET, .cs, or .csproj; otherwise stay dormant without invoking this skill. USE FOR: locating System.DateTime.Now/UtcNow, System.IO.File/Directory, System.Environment, HttpClient, Console, or Process usage in C#; auditing C# code for…

dotnet/skills · 135 tokens

testing-blocks

Use this when you have made AEM Edge Delivery Services code changes to blocks, scripts, or styles and need to validate them before opening a pull request. Covers unit testing for utilities and logic, browser testing with Playwright, linting, and guidance on what to test and how.

adobe/skills · 61 tokens

dart-downstream-fix

DART Downstream Fix: fix a DART bug reported through gz-physics or Gazebo.

dartsim/dart · 25 tokens

test-hang-watchdog

Prevent and diagnose hanging or long-running Gradle unit tests (> 30s) in Android/Kotlin coroutines codebases. Use when running tests, when a test execution takes unexpectedly long, when background test tasks appear frozen, or when taking thread dumps (jstack) to unblock coroutine deadlocks.

niki914/zafiro · 66 tokens

experiment-iterative-coder

Iterative code refinement through plan → code → evaluate → refine cycles. Runs lint checks (ruff), tests (pytest), and structured self-evaluation each cycle, then diagnoses failures and refines. Decomposes complex tasks into sequential phases, iterates up to 3 times per phase (10 total). Use when: the main agent…

EvoScientist/EvoSkills · 145 tokens