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...
Installs 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 with every re-scan.
[](https://www.skillsdirectory.com/skills/hoangnguyen0403-common-llm-security-12cde888)
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.
