persistent-planning — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited persistent-planning (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.
Use 3 persistent markdown files to track plans across sessions:
# Plan: [Feature Name]
## Goal
What we're building and why.
## Steps
1. [ ] Step one
2. [ ] Step two
3. [ ] Step three
## Constraints
- Must be backward compatible
- Must pass existing tests
## Status
IN PROGRESS | COMPLETED | BLOCKED# Project Context
## Architecture Decisions
- Using X because Y
- Chose A over B because C
## Key Files
- src/auth.ts - Authentication logic
- src/api/ - API endpoints
## Known Issues
- Rate limiting not implemented yetthoughts/PLAN.md exists, it's injected into contextthoughts/PROGRESS.md is auto-updated with commit hash and messagethoughts/ directory)thoughts/ to .gitignore if you don't want plans in version control~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.