A test-writing helper that finds the project's testing tools, reads the code, and creates tests for normal cases, edge cases, and errors. TDD means writing tests as part of the change, including tests that initially fail before the code is fixed.

Use it to add tests for JavaScript, Python, or Rust code, including integration tests and failure cases. It helps test public behavior without tying tests to internal implementation details.

It reduces the chance of missing important behavior or copying existing tests. It also checks that the new tests run and follow the project's existing patterns.

test — Skill by Supersynergy

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 skills/supersynergy/awesome-agentic-coding/test

Any agent

npx skills add Supersynergy/awesome-agentic-coding --skill test

Clone the repo

git clone --depth 1 https://github.com/Supersynergy/awesome-agentic-coding

Made for: Claude Code, Codex.

Per session 19 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 329 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.

Model	Per session	Once invoked
Fable 5	$0.00019	$0.00329
Opus 5	$0.00010	$0.00164
Sonnet 5	$0.00004	$0.00066
Haiku 4.5	$0.00002	$0.00033

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

Security

Grade A, and why

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

skills/test/SKILL.md · 37 lines

What it actually says

Test Writing Protocol

Target: $ARGUMENTS

Step 1: Detect Test Framework

Check package.json for vitest, jest, mocha, playwright
Check pyproject.toml / pytest.ini for pytest
Check Cargo.toml for Rust test config
Check existing test files for patterns

Step 2: Read the Code Under Test

Read the target file completely
Identify: public API, edge cases, error paths, dependencies
Check for existing tests (don't duplicate)

Step 3: Write Tests (TDD-Style)

Follow this priority:

Happy path — Does the basic case work?
Edge cases — Empty input, null, boundary values
Error paths — Invalid input, network failures, auth failures
Integration — Does it work with real dependencies?

Rules

Test BEHAVIOR, not implementation details
No mocks unless absolutely necessary (prefer real dependencies)
Each test should be independent — no shared mutable state
Descriptive test names: should return 404 when user not found
Run tests after writing: confirm they pass (or fail for TDD red phase)
Keep tests close to source: foo.test.ts next to foo.ts

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.

2d ago First seen · 37 lines · 19 tokens per session scan A 481af389a136

Subscribe to this mod's changes

test is a skill published in the GitHub repository Supersynergy/awesome-agentic-coding (1 stars, last pushed 1mo ago), licensed MIT. It adds 19 tokens to every session and 329 once invoked, about $0.0001 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-31.

TDD Testing agentic-coding ai-coding awesome-list best-practices claude claude-code

tdd-rust

TDD workflow for RTK filter development. Red-Green-Refactor with Rust idioms. Real fixtures, token savings assertions, snapshot tests with insta. Auto-triggers on new filter implementation.

rtk-ai/rtk · 45 tokens

rtk-tdd

Enforces TDD (Red-Green-Refactor) for Rust development. Auto-triggers on implementation, testing, refactoring, and bug fixing tasks. Provides Rust-idiomatic testing patterns with anyhow/thiserror, cfg(test), and Arrange-Act-Assert workflow.

rtk-ai/rtk · 61 tokens

linked-intent-dev

Guide for linked-intent development (LID). Consult for ALL code changes. Walks changes through a mode-aware six-phase workflow (HLD → LLD → EARS → intent-narrowing edge audit → tests-first → code) with mandatory stops between each phase. Bugs walk the arrow like any other change — no short-circuit. Enforces cascade…

jszmajda/lid · 87 tokens

test