spike — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited spike (Agent Skill) and scored it 92/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 2 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 2 flagged
The text {match} tells the agent to skip the normal "ask the user first" gate. Used adversarially it removes the human-in-the-loop check before destructive or sensitive actions, turning a normally-gated agent into a fire-and-forget executor.
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.
A spike is a time-boxed experiment to answer a question ("does this API work like I think?", "is this approach viable?"). Its only output is knowledge — the code is disposable.
spike is done when it's answered, not when the code "works".
point is to learn, not to ship — don't invest in code you'll throw away.
harder than expected — that's itself an answer; report it.
skill or memory if it'll recur).
scratch with test-driven-development — do NOT "clean up" the spike into production code; it carries hidden assumptions and skipped cases.
Red flag: a spike quietly becoming the implementation. Delete means delete.
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.