Individual skill
llm-app-security
Securing a feature that calls an LLM: prompt injection as an unsolved input problem, bounding what model output is allowed to reach, tool authorization against the human rather than the model, approval gates on consequential actions, RAG context provenance, system-prompt leakage, and cost limits. Use when sending prompts to an LLM API, building a RAG pipeline, giving a model tools, rendering or executing model output, or exposing an LLM-backed endpoint.
skills/llm-app-security/SKILL.md
Source commit eaba88102d91df65a9aa6397e8507c315c018f5e
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Network or broad shell
- Last checked
- Nov 6, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
Standard SKILL.md format has not been attested at this commit. No installation command is available; inspect the source.
Repository context
- Repository stars (not skill ratings)
- 23
- Repository last updated
- Aug 14, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- claude-skills Repository topic
- llm Repository topic
- security Repository topic
- skills Repository topic
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 8,635 bytesreferences/verifying-findings.mddoc · 3,520 bytesrules/prompt_injection_patterns.jsonasset · 2,167 bytestests/corpus.jsonasset · 2,140 bytes
Read excerpt
# LLM Application Security
## Rules (for AI agents)
### ALWAYS
- Start from the premise that **prompt injection is not solved at the prompt layer**.
A model has no privileged channel: system text, user text, a retrieved document and
a tool result all arrive as one context, and nothing in that context can be marked
as instructions the model must obey over the rest. Message roles are a formatting
convention, delimiters raise the cost of an attack, and an instruction such as
"treat the following as data" is itself just more text in the same window. Design
as though injection will sometimes succeed, and put the real controls after the
model rather than in front of it.
- Bound what the model's output is **allowed to reach**. Every downstream sink — a