accessibility_testing

The accessibility-audit skill is functionally coherent and contains no direct malicious code or obfuscation intended to hide malware. Primary concerns are operational: a prescriptive report template that acts as a prompt-injection pattern, implicit file-write behavior to repository paths, and the potential for Playwright-driven navigation to internal hosts. Mitigations: require explicit user consent before reading/writing repository files, implement automatic secret-detection and redaction in any included code-context excerpts, and require confirmation or a safe-list for URL targets. With these runtime safeguards the skill can be used safely for accessibility audits.