new-job — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited new-job (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
A bulleted imperative like {match} tells the agent to never reveal, disclose, or mention something to the user. Used adversarially it can instruct the agent to hide its tool calls or lie about what it did — stripping the transparency a user relies on to trust the agent.
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.
Add a new row to List.xlsx (Sheet1) with the bundled script. Do not write ad hoc openpyxl code.
/thanks pages are fine)done = applied (default)In progress = ONLY when a callback/response was receivedRejected = only when logging a rejection for a job that was never trackedclaude-job-agent/): python .claude/skills/new-job/scripts/add_job.py --company "Company" --role "Role" --url "https://..." [--status done] [--comment "..."]ADDED: row N (exit 0) → confirm company, role, status and row to the user.DUPLICATE (exit 2) → the same job URL is already tracked; tell the user the existing row, do not add.COMPANY EXISTS (exit 3) → show the existing rows. If it's a different role, re-run with --force.ERROR (exit 1) → e.g. Excel has the file open; ask the user to close it and retry.The script takes the shared tracker lock, backs up List.xlsx to backups/ before writing, and matches URLs ignoring www, query strings, trailing slashes and /thanks or /application suffixes.
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.