Test-Driven Development
Test-Driven Development is a community-maintained skill from obra/superpowers. Anomity scores its risk at 50 out of 100 (medium).
Analysis summary
Test-Driven Development is a community-maintained skill from obra/superpowers. Anomity scores its risk at 50 out of 100 (medium).
Test-Driven Development is a rigid process skill from the Superpowers plugin that enforces a strict red-green-refactor loop for any feature implementation or bug fix. Before the agent is allowed to write production code, the skill requires it to write a failing test that captures the desired behavior, watch that test fail for the right reason, write the minimum implementation that makes the test pass, and only then refactor with the test still passing as a guardrail.
Functionally, the skill reads existing test and source files to find the right place for new tests and code, and writes new test files plus implementation files as the agent moves through the loop. It does not request shell execution — the test runs themselves go through the Claude Code Bash tool — and it does not request network or credential access.
The skill is community trust because it ships in an independent plugin. The active risk signals come from filesystem read and write, the minimum surface for any skill that produces tests and code, and do not match any dangerous combination. The notable property of the skill is not its capability surface but its discipline: it actively prevents agents from skipping the test step when the underlying task is harder than expected.
Why this entry scored 50 out of 100
This profile starts at the catalog's neutral base of 50. Because the entry is community-maintained, trust adjusts the score by -10. Declared high-risk capabilities add +10 (capped at +30). It matches no dangerous capability combinations. The clamped result is 50, placing it in the medium band.
Findings
-
Established community project Trust offset
-
1 high-risk capability: filesystem:write High
Capabilities
Every capability the entry declares, with the security implication of each.
-
filesystem:readFilesystem readCan read files on the host system. Used for context, indexing, or analysis. -
filesystem:writeFilesystem writeCan create, edit, or delete files on the host system. High-impact capability — anything from helpful edits to planting persistence.