agentmods.dev

testing

testing is a skill for Claude Code, Codex from cynthiajones34/GBrain. It costs 63 tokens per session (2,080 once invoked), scanned A, a copy of testing, MIT.

A validation and test-health framework for checking add-on files, project tests, and regressions. A regression is a previously working behavior that has started failing.

In plain words
What is it for?
Use it to validate skills, run unit tests, evaluations, integrations, and system-health checks, and produce regression-aware reports.
Why use it?
It finds missing metadata and references, checks coverage, runs tests in stages, and classifies failures so problems are easier to understand.

Skill for Claude CodeCodex

Which agent this was written for is unclear — built for gbrain. 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.

not rated 0repo 2mo ago A scan 63 tokens copy · 100% MIT

Good fit Use it to validate skills, run unit tests, evaluations, integrations, and system-health checks, and produce regression-aware reports.

Compare 6 skills from other repositories ↓
View source ↗ cynthiajones34/GBrain thebuildersopsstudio.com
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/cynthiajones34/GBrain
agentmods
npx agentmods add skills/cynthiajones34/gbrain/testing

Made for: Claude Code, Codex.

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/cynthiajones34/gbrain/testing/github.svg)](https://agentmods.dev/skills/cynthiajones34/gbrain/testing)
Your own site
<a href="https://agentmods.dev/skills/cynthiajones34/gbrain/testing"><img src="https://agentmods.dev/badge/skills/cynthiajones34/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/cynthiajones34/gbrain/testing"><img src="https://agentmods.dev/badge/skills/cynthiajones34/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,080 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.
Origin 100% copy Near-identical to another mod 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.02080
Opus 5.5 $0.00025 $0.00832
Sonnet 5.5 $0.00013 $0.00416
Haiku 4.5 $0.00006 $0.00208

Measured 1mo ago against content hash f1846ba7c350, 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 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.

Origin

This is a copy

100% identical to testing — 8 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.

skills/testing/SKILL.md · 259 lines

How it starts

The opening of the file, as written. The whole thing — 259 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 · 259 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. 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 cynthiajones34/GBrain (0 stars, last pushed 2mo ago), licensed MIT. It adds 63 tokens to every session and 2,080 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to testing, differing in 8 lines, and is treated as a copy.

Cost OptimizationTestingai-agentboutique-consultancygbrainhermes-agentknowledge-graph
Related

Other skills, from other repositories

pptx-html-fidelity-audit

Audit a python-pptx export against its source HTML deck, identify layout/content drift (footer overflow, cropped content, missing italic/em, lost styling, off-rhythm spacing), and re-export with strict footer-rail + cursor-flow layout discipline. Use this skill whenever the user has a .pptx that was generated from an…

nexu-io/open-design · 185 tokens

build-test

Run the project's build / typecheck / lint / test commands and emit the build.passing + tests.passing signals devloop convergence reads.

nexu-io/open-design · 31 tokens

potpie-debug-memory

Use while debugging or troubleshooting failures, flaky tests, incidents, production alerts, CI failures, local dev setup issues, repeated bugs, prior fixes, failed attempts, and verification history.

potpie-ai/potpie · 41 tokens

potpie-project-preferences

Use before writing, modifying, reviewing, refactoring, or testing code so repo/project preferences surface: error handling, file structure, frameworks, logging, dependency choices, testing, security, API style, and naming. Also use after code work when a reusable project preference should be recorded.

potpie-ai/potpie · 63 tokens

hugegraph-regression-tester

Route HugeGraph MCP regression testing tasks to the current public tool surface, including inspection, read-only queries, Gremlin generation, extraction, controlled import, schema validate/dry-run, safety guards, and admin-gated tool checks.

apache/hugegraph-ai · 54 tokens

closed-loop

Run one task through the V-model verification loop: CP-2 plan → CP-3 build → CP-3v component verify → CP-4 integration verify (full lane) → CP-5 acceptance. The worker never grades its own homework; evidence rows trace back to AC-n. Opt-in: invoke with /closed-loop or by asking for the closed loop, proper…

huytieu/COG-second-brain · 0 tokens