SkillsMay 11, 2026·2 min read

llm-guard — Secure LLM Inputs & Outputs

Harden LLM apps with a scanner pipeline for prompt injection, PII leakage, toxicity, and unsafe output. Install in minutes and gate requests in code.

Script Depot
Script Depot · Community
Agent ready

Ready-to-run agent install

This asset can be installed after the agent chooses its runtime, checks the plan, and runs the matching command.

Native · 98/100Policy: allow
Agent surface
Any MCP/CLI agent
Kind
Skill
Install
Single
Trust
Trust: Established
Entrypoint
Asset
Direct install command
npx -y tokrepo@latest install d1888a22-7087-4310-bcaa-dca6663a2e18 --target codex

Run after dry-run confirms the install plan.

Intro

Harden LLM apps with a scanner pipeline for prompt injection, PII leakage, toxicity, and unsafe output. Install in minutes and gate requests in code.

  • Best for: Teams shipping LLM features who need a practical, code-first safety layer before production
  • Works with: Python, any LLM provider, sync/async app servers (FastAPI, Celery, etc.)
  • Setup time: 10 minutes

Quantitative Notes

  • Setup time ~10 minutes (pip install + one scanner chain)
  • GitHub stars + forks (verified): see Source & Thanks
  • Typical pipeline: 3–6 scanners (prompt injection + secrets/PII + output safety)

Practical Notes

A reliable rollout pattern is: start with one high-signal guard (prompt injection / secrets) in monitor mode, log detections, then switch to block/redact. Keep scanner configs versioned, and add allowlists for known-safe internal tools to reduce false positives.

Safety note: Do not rely on a single prompt to prevent injection—enforce guardrails in code with logs, tests, and allowlists.

FAQ

Q: What problem does it solve? A: It adds an explicit scanning/guard layer to LLM inputs and outputs to reduce prompt injection, leakage, and harmful content.

Q: Is it a model or a rule engine? A: It’s a toolkit. You compose scanners/filters (rules + detectors) around whichever LLM you already use.

Q: Where should I enforce it? A: Enforce on both edges: before the model call (prompt) and before returning to users (output).

🙏

Source & Thanks

GitHub: https://github.com/protectai/llm-guard Owner avatar: https://avatars.githubusercontent.com/u/102992336?v=4 License (SPDX): MIT GitHub stars (verified via api.github.com/repos/protectai/llm-guard): 2,941 GitHub forks (verified via api.github.com/repos/protectai/llm-guard): 391

Discussion

Sign in to join the discussion.
No comments yet. Be the first to share your thoughts.

Related Assets

Guardrails — Validate & Secure LLM Outputs

Guardrails is a Python framework for validating LLM inputs/outputs to detect risks and generate structured data. 6.6K+ GitHub stars. Pre-built validators, Pydantic models. Apache 2.0.

Skills
Script Depot

Guardrails AI — Validate LLM Outputs in Production

Add validation and guardrails to any LLM output. Guardrails AI checks for hallucination, toxicity, PII leakage, and format compliance with 50+ built-in validators.

Skills
Agent Toolkit

Tauri — Smaller, Faster, More Secure Desktop Apps in Rust

Tauri lets you build smaller, faster, and more secure desktop and mobile applications with any web frontend. Rust backend + OS native WebView (no bundled Chromium) produces ~3MB binaries compared to Electron 150MB.

Skills
Script Depot

NeMo Guardrails — Programmable Safety for LLM Applications

NeMo Guardrails is an open-source toolkit by NVIDIA for adding programmable guardrails to LLM-based conversational systems. It provides input/output moderation, fact-checking, hallucination detection, jailbreak prevention, and dialog management via a declarative Colang configuration language.

Skills
Script Depot
◈Home🔍Search👤Me