agno-security

Applies OWASP security practices to Agno agents and FastAPI production APIs.

Updated Sep 10, 2026
One-click install
npx skills add https://github.com/allankltsn/setup_kiro --skill agno-security-allankltsn
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: agno-security
Source: https://github.com/allankltsn/setup_kiro/tree/main/.kiro/skills/agno-security
Command: npx skills add https://github.com/allankltsn/setup_kiro --skill agno-security-allankltsn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Deploying an LLM agent to production exposes it to prompt injection, data leakage, cost abuse, and API-level attacks, and most teams lack a single end-to-end security map covering both the agent and its HTTP boundary. ## Core Features & Use Cases - Two-layer defense model: Covers agent/LLM security (OWASP LLM Top 10: prompt injection, PII leakage, token budget abuse, least-privilege tools) and FastAPI REST API security (OWASP API Top 10: JWT validation, authz per resource, rate limiting, CORS, TLS, secure headers). - Critical FastAPI blockers: Lists 11 mandatory production items including real JWT validation, bcrypt/argon2 password hashing, refresh tokens, CSRF, SQL injection prevention, secure file upload, TrustedHost, and dependency scanning with bandit/pip-audit/safety. - Production checklist: Provides a ready-to-use security checklist spanning agent guardrails, API hardening, IAM least-privilege, secrets management, and WAF/DDoS edge protection. - Use Case: Before exposing an Agno agent behind API Gateway and FastAPI, walk the checklist to confirm guardrails are active, JWT is properly validated, errors leak no stack traces, and dependencies are pinned and audited in CI. ## Quick Start Ask the agent to review your FastAPI agent deployment against the production security checklist and identify which critical items are missing.

Frequently Asked Questions about agno-security

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I secure an LLM agent for production deployment?▼

Secure an LLM agent by enforcing mandatory guardrails for prompt injection, scope, and PII, treating all user input and tool outputs as untrusted, limiting max_tokens and input size, and giving tools least-privilege access with validated arguments.

How do I add JWT authentication to a FastAPI agent API?▼

Add JWT authentication using FastAPI's HTTPBearer security dependency and validate the token's signature, expiration, audience, and issuer before accepting it. Return 401 with WWW-Authenticate: Bearer on failure, and authorize per resource using token claims to prevent BOLA/IDOR.

What are the critical security items for FastAPI in production?▼

Critical items include real JWT validation, bcrypt/argon2 password hashing, short-lived access tokens with refresh tokens, CSRF protection for cookie flows, parameterized queries, secure file upload validation, full security headers with TrustedHost, disabled debug routes, and dependency scanning in CI.

Does this approach work with serverless deployments on AWS Lambda?▼

Yes, the model assumes FastAPI behind API Gateway on Lambda, where TLS termination, throttling, and WAF/DDoS protection live at the edge. The Lambda role must follow least-privilege IAM, limited to only the Bedrock, Secrets Manager, S3, and DynamoDB actions it uses.

Why should agent logs never contain prompts or responses?▼

Prompts and responses can contain PII or secrets, so logging them creates a data leakage channel. Log only metadata such as token counts, latency, and guardrail triggers, and keep error responses to clients neutral without stack traces.