vibe-how-do-we-do — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited vibe-how-do-we-do (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 canonical vibe as the only governed runtime authority for this request.
Entry bias:
xl_planExecution rules:
vibevibe as the only runtime authorityvibe keep router selection and confirm_required ownershipplan_execute or phase_cleanup unless the user explicitly re-enters through canonical vibe or another approved wrapperruntime-summary.json exposes bounded_return_control.explicit_user_reentry_required = true, forward --continue-from-run-id <source_run_id> and --bounded-reentry-token <reentry_token> before launching this wrapperWhen this wrapper is chosen, enter canonical vibe with:
xl_planxl_planRequest: $ARGUMENTS
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.