give-plan — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited give-plan (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.
ultrathink
Figure out the right approach, write a plan the user can inspect, and stop. Planning is not approval to implement — wait for explicit go-ahead before writing any code.
If already in native plan mode, this skill shapes how to plan; plan mode provides the workflow structure and must follow this skill guidelines.
Check conversation context and skip completed steps.
What kind of plan? Scoped implementation, phased feature, migration/rollout, architecture decision, or spec artifact. Ask only the questions that matter.
Read relevant files and search the codebase before proposing changes. Be explicit about what's confirmed from code vs. inferred vs. unknown.
Don't force every request into the same template.
Match artifact to plan size — don't force plans/*.md on small scoped changes.
Use date +%Y%m%d%H%M%S for timestamps.
A strong plan covers: problem summary, recommended approach, phases/workstreams, affected files/modules/systems, dependencies and sequencing, validation strategy, risks and mitigations, assumptions and open questions, non-goals when useful.
Summarize the recommendation, call out risks/assumptions/unknowns, clarify what needs user confirmation, then wait. Do not drift into coding.
<request>$ARGUMENTS</request>
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.