test-assertions

A command that rewrites tests to check complete expected values with strict equality. Tests are checks that verify code behaves as intended; strict equality also distinguishes missing values from undefined values and different object types.

In plain words
What is it for?
Use it to rewrite selected test files, changed tests, or all tests so objects and arrays use strict deep-equality assertions.
Why use it?
It replaces weak checks that may let incorrect or extra data pass, making failures show the full difference between the result and the expected value.

Command

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.

agentmods
npx agentmods add commands/motlin/claude-code-plugins/test-assertions
Clone the repo
git clone --depth 1 https://github.com/motlin/claude-code-plugins
Per session 8 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,591 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00008 $0.01591
Opus 5 $0.00004 $0.00796
Sonnet 5 $0.00002 $0.00318
Haiku 4.5 $0.00001 $0.00159

Measured 2d ago against content hash dd6ca572bc2b, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

test-assertions 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 2d 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.

plugins/code/commands/test-assertions.md · 178 lines

How it starts

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

Rewrite tests to use strict deep equality assertions everywhere.

This is a full rewrite, not incremental tweaking. Rethink each test holistically. Collapse multiple weak assertions about the same value into a single strict equality check against the complete expected value.

Assertion ranking (worst to best)

Only toStrictEqual is good enough. Everything else is too weak:

  1. toBeTruthy, toBeDefined, not.toBeNull — barely checks anything
  2. toHaveProperty('key') — only checks existence, not value
  3. toContain, toMatch — substring/regex match hides the full value
  4. toHaveLength(n) — only checks count, not contents
  5. toMatchObject, objectContaining, arrayContaining — allows extra properties to sneak in
  6. toEqual, to.deep.equal — close, but ignores class mismatches and undefined vs missing
  7. toStrictEqual — the only acceptable assertion for objects and arrays

Scope

Determine which test files to rewrite:

  • If $ARGUMENTS is provided, use that file or directory
  • If $ARGUMENTS is empty and there are uncommitted changes, find test files among the unstaged/staged changes
  • If $ARGUMENTS is empty and there are no uncommitted changes, find all test files in the project

Process

  • Identify the target test file(s) using the scope rules above
  • For each test, identify every assertion
  • Replace weak assertions with a placeholder like expect(result).toStrictEqual({}) — do NOT guess the expected value from reading the implementation
  • Run the test and let the error message reveal the actual value
  • Copy the actual value from the error output into the assertion
  • Run the test again to confirm it passes

What to rewrite

Multiple weak assertions on the same value become one strict assertion

// Before: three assertions that barely check anything
const result = await Children.run(['--json', '--projects-dir', '/tmp/fake-projects']);
expect(result).toHaveProperty('projects');
expect(result).toHaveProperty('summary');
expect(result.summary.total).toBe(2);

// Step 1: replace with placeholder — do NOT guess the expected value
expect(result).toStrictEqual({});

// Step 2: run the test, read the actual value from the error output, paste it in
expect(result).toStrictEqual({
	projects: [
		{name: 'project-a', path: '/tmp/fake-projects/project-a'},
		{name: 'project-b', path: '/tmp/fake-projects/project-b'},
	],
	summary: {total: 2, active: 2},
});

Read the full file on GitHub · 178 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. 2d ago First seen · 178 lines · 8 tokens per session scan A dd6ca572bc2b

Subscribe to this mod's changes

test-assertions is a command published in the GitHub repository motlin/claude-code-plugins (15 stars, last pushed 3d ago), licensed Apache-2.0. It adds 8 tokens to every session and 1,591 once invoked, about $0.0000 per session on Opus 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.