Is hyper-tdd safe to install?

SaferSkills independently audited hyper-tdd (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.

CategoryWeightCategory scoreContribution

Securityprompt, exec, net, exfil, eval

35%

100

35.0 pts

Supply chainhash, typosquat, maintainer, lockfile

20%

100

20.0 pts

Maintenancestaleness, pinning, CI

15%

100

15.0 pts

TransparencySKILL.md, perms, README

15%

100

15.0 pts

Communityinstalls, verify, response

15%

100

15.0 pts

Findings & checks · 0 flagged

Securityscore 100 · 0 findings

✓—All security checks passedNo findings in this category for the latest scan.pass

Supply chainscore 100 · 0 findings

✓—All supply chain checks passedNo findings in this category for the latest scan.pass

Maintenancescore 100 · 0 findings

✓—All maintenance checks passedNo findings in this category for the latest scan.pass

Transparencyscore 100 · 0 findings

✓—All transparency checks passedNo findings in this category for the latest scan.pass

Communityscore 100 · 0 findings

✓—All community checks passedNo findings in this category for the latest scan.pass

The primary manifest — the file an agent reads to learn what this artifact does.

skills/hyper-tdd/SKILL.md · 1 file

skills/hyper-tdd/SKILL.md1.6 KB · Markdown

name: hyper-tdd

description: Use when about to write or modify behavior-bearing code — functions, business logic, bug fixes — before writing any production code. Also when the user invokes /hyperclaude:hyper-tdd. Forces a failing test first so you watch it fail for the right reason.

hyper-tdd

Test-driven discipline tailored to this author's preferences.

The loop

Write the failing test first. Name the behavior, not the implementation. The test should compile/import but fail because the behavior doesn't exist yet.
Run it. Confirm it fails for the right reason. "Cannot find function" is fine. "ReferenceError because of typo in test" is not — fix the test.
Write the minimum code to make it pass. Resist scope creep. No "while I'm here" edits.
Run it. Confirm it passes.
Commit. One behavior, one commit. Commit messages describe the behavior, not the code.
Refactor if there's a clear smell. Tests must still pass after.

Skip TDD when

Touching only documentation, comments, or formatting.
Renaming a symbol (an LSP/grep operation, not a behavior change).
One-shot migration scripts that run once and get deleted.
Config-only changes (e.g., updating a .gitignore).

What "minimum" means here

Implement only what the current test requires. If you need a helper, add the simplest version. Do not pre-build for tests you might write later — write that test first, then the helper.

What good test names look like

✅ slugify drops non-ASCII characters
✅ cli --dry-run prints JSON without spawning codex
❌ test_slugify (says nothing)
❌ slugify works correctly (vague)

hyper-tdd— agent skill

Is hyper-tdd safe to install?

hyper-tdd

The loop

Skip TDD when

What "minimum" means here

What good test names look like

Audit the pieces. Scan the whole. Decide.