verify-docs — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited verify-docs (Agent Skill) and scored it 45/100 (orange). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 1 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 1 flagged
A base64 string of 128+ characters appears in a documentation file. Encoded prompt injection hides the hostile instruction in base64 — invisible to keyword filters — and relies on the agent's ability to decode it at runtime. There is no normal authoring reason to embed a multi-hundred-byte base64 blob in skill docs.
*.sig, SIGNATURES) outside the documentation.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.
Run the document generation verification loop to check that generated Office files are structurally valid, open in Python libraries, and roundtrip through AILANG Parse correctly.
Three levels of verification on all files in data/examples/:
Run the verification script:
uv run --with python-pptx --with openpyxl --with python-docx benchmarks/verify_generated.pyIf generator code has changed, regenerate demo files first, then verify:
bash .claude/skills/verify-docs/scripts/regen_and_verify.shbash .claude/skills/verify-docs/scripts/verify_only.shWhen this skill is invoked:
--regen or asked to regenerate filesscripts/regen_and_verify.sh which generates fresh demo files across all formats then verifiesscripts/verify_only.shcreateArchive limitation (no store/no-compress flag). Shows as WARN, not FAIL.~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.