test-driven-development — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited test-driven-development (Agent Skill) and scored it 92/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 2 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 2 flagged
The text {match} tells the agent to skip the normal "ask the user first" gate. Used adversarially it removes the human-in-the-loop check before destructive or sensitive actions, turning a normally-gated agent into a fire-and-forget executor.
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
Use this whenever you add or change behaviour. The discipline is what makes the test trustworthy — a test you never saw fail proves nothing.
test that asserts it, using real code (no mocks unless a dependency is truly unavailable). One behaviour per test; name it for the behaviour.
is missing), not a typo or import error. If it passes already, you're testing existing behaviour — fix the test.
options, abstractions, or features the test doesn't demand.
is clean (no new warnings).
behaviour here.
If a test is hard to write, the design is usually too coupled — simplify the interface before continuing.
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.