create-test-plan-40ae4c — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited create-test-plan-40ae4c (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.
Findings & checks · 0 flagged
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.
Analyze what changed and generate a comprehensive test plan covering four escalating levels of testing depth.
Resolve scope using the first match:
After identifying scope, read the actual code in depth to understand:
Always check for project-specific testing skills or MCP tools first. Use the fallbacks below when nothing project-specific is available:
/agent-browser skill if available, otherwise claude-in-chrome MCPcomputer-use MCPFor each level, generate specific, actionable test scenarios tailored to the actual change. Each scenario needs exact steps and an expected outcome.
Does the feature work at all? Verify the happy path and the most obvious behavior.
Combine multiple actions in sequence. Verify state consistency across operations.
Actively try to break the feature. Explore boundary conditions and unexpected inputs.
Explore state interactions across system boundaries. These surface the hardest bugs.
If the change is small enough that a level has no meaningful scenarios (e.g., a typo fix has no cross-cutting scenarios), note "N/A for this change" with a brief explanation.
Output the plan as text. Then use AskUserQuestion to ask for approval before writing.
Create the .turbo/ directory if it does not exist. Write the plan to .turbo/test-plan.md using this format:
# Test Plan: <Feature/Change Name>
## Context
<Brief description of what changed and why>
## Approach
<Testing approach: agent-browser / claude-in-chrome / computer-use / terminal>
<Dev server command if applicable>
## Level 1: Basic Functionality
- [ ] **<Test name>** — <Steps to perform> → Expected: <expected outcome>
## Level 2: Complex Operations
- [ ] **<Test name>** — <Steps to perform> → Expected: <expected outcome>
## Level 3: Adversarial Testing
- [ ] **<Test name>** — <Steps to perform> → Expected: <expected outcome>
## Level 4: Cross-Cutting Scenarios
- [ ] **<Test name>** — <Steps to perform> → Expected: <expected outcome>~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.