Is strict-tdd safe to install?

SaferSkills independently audited strict-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.

library/methodologies/pilot-shell/skills/strict-tdd/SKILL.md · 1 file

library/methodologies/pilot-shell/skills/strict-tdd/SKILL.md2.1 KB · Markdown

name: strict-tdd

description: Strict RED->GREEN->REFACTOR test-driven development with enforcement. Never write production code before a failing test. Atomic commits per TDD cycle.

allowed-tools: Bash(*) Read Write Edit Glob Grep

metadata:

author: babysitter-sdk

version: "1.0.0"

category: pilot-shell-core

attribution: "Adapted from Pilot Shell by Max Ritter (https://github.com/maxritter/pilot-shell)"

strict-tdd

You are strict-tdd -- the test-driven development enforcement skill for Pilot Shell.

Overview

This skill enforces strict RED->GREEN->REFACTOR discipline across all implementations. It provides the rules, patterns, and verification methods for TDD compliance.

The Three Laws of TDD (Pilot Shell Strict Mode)

You may not write production code until you have a failing test
You may not write more of a test than is sufficient to fail
You may not write more production code than is sufficient to pass

TDD Cycle

RED Phase

Write a test that captures exactly one acceptance criterion
Run the test -- it MUST fail
Verify it fails for the RIGHT reason (not a syntax error)
Commit: test: add failing test for [criterion]

GREEN Phase

Write the MINIMUM code to make the test pass
Run the test -- it MUST pass
Verify only the target test turned green (no side effects)
Commit: feat: implement [criterion]

REFACTOR Phase

Clean up code while keeping ALL tests green
Remove duplication, improve naming, extract methods
Run full test suite -- ALL tests MUST pass
Commit: refactor: clean up [area]

Compliance Scoring

Score	Meaning
90-100	Exemplary TDD: all cycles followed correctly
70-89	Good TDD: minor deviations
50-69	Partial TDD: some implementation before tests
0-49	TDD violation: significant implementation without tests

Verification Methods

Git History Analysis: Test files must appear in commits before implementation files
Coverage Analysis: New code must have >90% test coverage
Commit Message Convention: RED/GREEN/REFACTOR phases identifiable in messages

strict-tdd— agent skill

Is strict-tdd safe to install?

strict-tdd

Overview

The Three Laws of TDD (Pilot Shell Strict Mode)

TDD Cycle

RED Phase

GREEN Phase

REFACTOR Phase

Compliance Scoring

Verification Methods

Audit the pieces. Scan the whole. Decide.