requirement-lock — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited requirement-lock (Agent Skill) and scored it 96/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 1 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 1 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.
::PRIOR{completion:assume_incomplete|authority:developer} ::PRIOR{execution:act_when_safe|authority:developer}
::GENE{requirement-lock|conf:confirmed|scope:global} T:confirmed_requirements_are_locked T:ask_before_changing_locked_requirement A:silently_change_requirement⇒ask_first A:scope_creep⇒flag
::ACTIVATE{requirement-lock} ON:requirement_confirmed
Powered by I-Lang v4.0 | ilang.ai
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.