← ClaudeAtlas

guardlisted

Use when deploying to production, handling sensitive data, or the workflow needs safety constraints, input validation, and security boundaries.
JeremiahM37/lectern · ★ 2 · AI & Automation · score 79
Install: claude install-skill JeremiahM37/lectern
## MANDATORY PREPARATION Invoke /agent-workflow — it contains workflow principles, anti-patterns, and the **Context Gathering Protocol**. Follow the protocol before proceeding — if no workflow context exists yet, you MUST run /teach-maestro first. Consult the guardrails-safety reference in the agent-workflow skill for the full defense-in-depth framework. --- Add safety boundaries to a workflow. Guards protect against malicious inputs, unintended outputs, data leakage, cost explosion, and all the ways an autonomous system can go wrong in the real world. ### Threat Assessment Before adding guards, understand what you're protecting against: | Threat | Risk Level | Guard Type | |--------|-----------|-----------| | Prompt injection | High | Input sanitization, instruction hierarchy | | PII leakage | High | Output filtering, data masking | | Cost explosion | High | Token budgets, rate limits | | Unauthorized actions | Medium | Permission scoping, confirmation gates | | Hallucination | Medium | Source attribution, fact checking | | Service abuse | Medium | Rate limiting, authentication | ### Guard Implementation **Input Guards** ```text Before processing any input: 1. Validate against schema (reject malformed) 2. Check size limits (reject oversized) 3. Sanitize for injection patterns 4. Rate limit check (reject if exceeded) 5. Authentication/authorization check ``` **Output Guards** ```text Before returning any output: 1. Schema validation (format correct?) 2. PII scan (