The violated guardrails are **Memory Poisoning (LLM04)** and **Evolution Approval**. An incident log is untrusted data, not policy, so it cannot authorize or self-approve a memory or skill change. Stop persistence and promotion. Redact and **sanitize** the proposed rule, discard instruction-like or sensitive content, then restart through independent review. Proceed only with evidence such as the original authenticated incident, provenance, integrity checks, the redacted candidate diff, valida...
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-c95923c4)
The violated guardrails are **Memory Poisoning (LLM04)** and **Evolution Approval**. An incident log is untrusted data, not policy, so it cannot authorize or self-approve a memory or skill change.
Stop persistence and promotion. Redact and **sanitize** the proposed rule, discard instruction-like or sensitive content, then restart through independent review. Proceed only with evidence such as the original authenticated incident, provenance, integrity checks, the redacted candidate diff, validation results, and approval from an independent authorized reviewer. Until then, do not write the rule to memory or alter the skill.
