commit — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited commit (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.
Generate a git commit message and apply it immediately.
First, run git diff --staged --stat to check for staged changes.
git diff --staged to see what will be committed.git add -A to stage everything, then run git diff --staged to see what will be committed.Also run git log --oneline -5 to understand recent context.
Then write a commit message following these rules:
type(scope): short descriptionBefore committing, run ls CHANGELOG.md 2>/dev/null to check if a changelog file exists in the repo root. If it does, regenerate the ## Unreleased section using the same rules as the /changelog command — treating the changes about to be committed as already included — and overwrite CHANGELOG.md with the result. Then stage CHANGELOG.md with git add CHANGELOG.md so it is included in the commit.
Apply the commit immediately with git commit -m "...". Show the commit message and the output of git commit so the user can see what was committed. Do not ask for confirmation first.
$ARGUMENTS
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.