testing-standards

testing-standards is a skill for Claude Code, Codex from anatomia-dev/anatomia. It costs 34 tokens per session (880 once invoked), scanned A, original, MIT.

Project-specific standards for writing and reviewing Vitest tests, a JavaScript and TypeScript testing tool.

In plain words
What is it for?
Use them when adding tests, reviewing test quality, or setting up test infrastructure in this project.
Why use it?
They help tests check real behavior, include failure cases, and avoid passing without proving anything.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use them when adding tests, reviewing test quality, or setting up test infrastructure in this project.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/anatomia-dev/anatomia/testing-standards
Install

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.

Any agent
npx skills add anatomia-dev/anatomia --skill testing-standards
Clone the repo
git clone --depth 1 https://github.com/anatomia-dev/anatomia

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-standards

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/anatomia-dev/anatomia/testing-standards"><img src="https://agentmods.dev/badge/skills/anatomia-dev/anatomia/testing-standards.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 34 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 880 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 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.00034 $0.00880
Opus 5.5 $0.00014 $0.00352
Sonnet 5.5 $0.00007 $0.00176
Haiku 4.5 $0.00003 $0.00088

Measured 2mo ago against content hash 1f93113d780e, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

testing-standards 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 2mo 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.

.ana/skills/testing-standards/SKILL.md · 38 lines

How it starts

The opening of the file, as written. The whole thing — 38 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Testing Standards

Detected

  • Framework: Vitest (199 test files)
  • Test command: pnpm run test -- --run
  • Testing patterns: vitest
  • Test location: dedicated test directory

Library Rules

  • Always pass --run flag when invoking Vitest in CI or non-interactive contexts. Vitest defaults to watch mode, which hangs pipelines waiting for input.

Rules

  • Test behavior, not implementation. Assert on what the code returns or produces — not which internal functions it calls. Tests should survive refactoring when behavior is unchanged.

  • Prefer real implementations over mocks. Mock only what you can't control: network calls, time, randomness. Every mock is a lie about how the system actually behaves.

  • Cover the error path, not just the happy path. For each feature test, write at least one test for invalid input, missing data, or service failure.

  • Assert on specific expected values from real inputs. expect(status).toBe(200) not expect(status).toBeDefined(). A test that passes regardless of whether the feature works catches nothing. Never write tautological tests — expect(true).toBe(true) proves nothing. The same applies to range matchers — toBe(2) not toBeGreaterThan(0) when the test fixture has a known count. If you can't determine the specific expected value, read the contract's matcher/value fields before falling back to a weak assertion. When a test assertion matches the contract's matcher and value, the test is contract-aligned — not weak.

  • Never weaken a test to make it pass. If a test fails, fix the code or fix the expectation — never broaden assertions or catch exceptions to force green.

  • When overriding EngineResult fields in tests, spread at each nesting level: { ...base, commands: { ...base.commands, test: 'vitest' } }. Never reconstruct the full object manually — the factory provides all required defaults and the type has 40+ fields.

  • Never assert on source code content as a proxy for testing behavior — mock the trigger and assert on the output. Source-content assertions are acceptable as enforcement tests: verifying template content, security constraints, or structural invariants where the file content itself is what's being enforced.

  • Run the relevant test file after each change for fast feedback: pnpm vitest run tests/{file}. Run the full suite before the build report to catch cross-file regressions.

  • Scan integration tests run against the compiled dist/index.js, not source. The pre-commit hook runs (cd packages/cli && pnpm run build) to keep the artifact fresh. If running tests manually outside the hook, run (cd packages/cli && pnpm run build) first — stale dist will give false passes on terminal output tests.

  • Tests that create git repositories must force the branch name with git init -b main or git branch -M main after first commit. CI runners have different init.defaultBranch settings — never assume the default. This has caused CI failures 3 times.

  • Use inline fixture data for scanner and parser tests — write files to temp directories at test time. Standalone manifest files with real package names (requirements.txt, package.json) trigger GitHub security advisory false positives.

  • Functions exported solely for test access (imported only by test files) are intentional — TypeScript has no internal keyword. Only flag exports with zero imports anywhere.

  • When a test searches for expected output (find, findIndex, match on stdout or result arrays), assert the search succeeded — don't gate assertions behind a truthy check. if (line) { expect(line).toContain(x); } silently passes when the output is missing. Write expect(line).toBeDefined() first, then assert the value. For optional detection results where absence is a valid test outcome, conditional checks are correct.

Read the full file on GitHub · 38 lines

Files

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.

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. 2mo ago First seen · 38 lines · 34 tokens per session scan A 1f93113d780e

Subscribe to this mod's changes

testing-standards is a skill published in the GitHub repository anatomia-dev/anatomia (32 stars, last pushed 2mo ago), licensed MIT. It adds 34 tokens to every session and 880 once invoked, about $0.0001 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.

Related

testing-standards compared with skills from other repositories

testing-standards next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
testing-standardsanatomia-dev/anatomiaSkill322mo agoMITA34Claude Code, Codex
scaffold-projectMarve10s/Better-FullstackSkill823yesterdayMITA80Claude Code
add-to-projectMarve10s/Better-FullstackSkill823yesterdayMITA71Claude Code
agent-dependenciesNVIDIA/elementsSkill119yesterdayApache-2.0A73Claude Code, Codex
adding-a-commandcaliber-ai-org/ai-setupSkill1.3k1mo agoMITA76Claude Code, Codex
agent-debug-ciNVIDIA/elementsSkill119yesterdayApache-2.0A80Claude Code, Codex
audit-ciNVIDIA/elementsSkill119yesterdayApache-2.0A78Claude Code, Codex