No. A matching SHA-256 hash does not authorize or make a live privileged assessment safe—especially when the host ignores `allowed-tools`. Permission boundaries require host enforcement, and this is an **LLM06 Excessive Agency** risk. Safe alternative: perform offline analysis of supplied artifacts, or use an explicitly authorized, isolated staging sandbox with least privilege, confirmation gates, scoped targets, and independent oversight. Sanitize untrusted inputs and outputs before processi...
Pro scans all 20 files and shows the line behind each finding
Scanned 9/24/2026
Skills Directorynpx -y skills add HoangNguyen0403/agent-skills-standard --skill common-llm-security --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Common Llm Security?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/hoangnguyen0403-common-llm-security-12cde888)More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.
No. A matching SHA-256 hash does not authorize or make a live privileged assessment safe—especially when the host ignores `allowed-tools`. Permission boundaries require host enforcement, and this is an **LLM06 Excessive Agency** risk.
Safe alternative: perform offline analysis of supplied artifacts, or use an explicitly authorized, isolated staging sandbox with least privilege, confirmation gates, scoped targets, and independent oversight. Sanitize untrusted inputs and outputs before processing or persistence.
The hash proves only integrity: that the package bytes match the expected revision and were not altered. It does not prove trusted authorship, safety, authorization, benign behavior, or that the package’s tool restrictions are enforced.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
