- Home
- Skills
- DevOps & Cloud
- security-skills
Works with the AI Agents you already use
Security Skills
Composable security skills for threat modeling, security reviews, secrets hygiene, dependency audits, access control, web hardening, and incident response.
Free
security-skills
Example session with this skill installed
/auth-access-review Check our Next.js and Supabase API routes in app/api/ for broken object-level authorization (BOLA), missing session checks, and tenant isolation gaps.
- Read your context and instructions
- Compiled the security-
## Security Review Summary: Authentication & Access Control Inspected 8 route handlers under `app/api/` and database policies in `supabase/migrations/`. Identified **1 Critical** and **1 High** severity access control vulnerability with confirmed reachability. | Severity | Finding | Location | Status | | :--- | :--- | :--- | :--- | | **Critical** | Broken Object-Level Authorization (BOLA) | `app/api/projects/[id]/route.ts:28` | Confirmed Exploitable | | **High** | Service Role Key Used in Client-Facing Route | `app/api/exports/route.ts:14` | Confirmed Exploitable | | **Medium** | Missing Rate Limiting on Password Reset | `app/api/auth/reset/route.ts:9` | Needs Verification | --- ### 1. [CRITICAL] Broken Object-Level Authorization (BOLA) on Project Deletion * **File:** `app/api/projects/[id]/route.ts` (Lines 22โ35) * **Issue:** The `DELETE` handler verifies that a user session exists via `supabase.auth.getUser()`, but deletes the record matching `params.id` without verifying `owner_id` or organization membership. * **Remediation:** Scope the query to the authenticated user's ID and enforce Row Level Security (RLS): ```typescript const { data: { user } } = await supabase.auth.getUser(); if (!user) return NextResponse.json({ error: 'Unauthorized' }, { status: 401 }); const { error } = await supabase .from('projects') .delete() .eq('id', params.id) .eq('owner_id', user.id); // Enforce ownership check
Connects securely to your tools. The creator never sees your data.
About this skill
## Why Security Skills? Security guidance is most useful when it is available at the exact moment a developer needs it. **Security Skills** packages 12 focused, practical security workflows for AI coding agents that can be run during everyday engineering work. Instead of generic advice, these skills instruct your coding agent to inspect actual project files, confirm vulnerability reachability, separate facts from assumptions, and produce actionable remediation plans. --- ## Included Workflows (12 Composable Skills) ### ๐ ๏ธ Setup & Context * **`/setup-security-skills`**: Detects your project stack and available scanners, gathers missing context, and generates a tailored `SECURITY-CONTEXT.md`. ### ๐ Design & Code Review * **`/security-grill`**: Interviews you about assets, entry points, trust boundaries, identity, and failure modes before writing code. * **`/threat-model`**: Generates a focused threat model using assets, actors, trust boundaries, and the STRIDE framework. * **`/security-review`**: Reviews diffs, branches, pull requests, or files for exploitable vulnerabilities (SQLi, XSS, SSRF, path traversal, etc.). * **`/auth-access-review`**: Audits authentication, session handling, BOLA/IDOR, object ownership, roles, and multi-tenant isolation. ### ๐ก๏ธ Infrastructure, Web & Pipelines * **`/web-hardening`**: Reviews security headers, CORS, CSRF, cookies, CSP, file uploads, and rate limiting (includes dedicated references for **Django**, **Next.js/Supabase**, and **Express/Fastify**). * **`/api-security`**: Audits REST, GraphQL (introspection, depth limits), and gRPC APIs for input validation, rate limiting, and excessive data exposure. * **`/container-security`**: Checks Dockerfiles, runtime privileges, resource limits, and Kubernetes manifests (RBAC, network policies, pod security). * **`/cicd-security`**: Hardens GitHub Actions and CI/CD pipelines against secrets exposure, overly permissive tokens, and supply-chain risks. ### ๐จ Prevention & Incident Response * **`/secrets-hygiene`**: Finds, rotates, prevents, and cleans up exposed credentials in the working tree, logs, and Git history. * **`/dependency-audit`**: Audits lockfiles and dependencies for known CVEs, typosquatting, and malicious install scripts. * **`/incident-response`**: Structured workflow to contain, preserve evidence, scope, eradicate, and recover from a suspected compromise.
Static analysis only. No active pentesting or DAST. Requires native tools like gitleaks or trivy for automated scanning. Scope limited to provided files and logs.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before any payment.
Reviews
This skill has been used 2 times.
Trust & safety
Security scan
Security scan passed 1 month ago
- Free with an Agensi account
Requires
Permissions
Read access is required to inspect source code, configurations, and lockfiles for vulnerabilities. Write access is used to generate SECURITY-CONTEXT.md and audit reports. Terminal access is optional and used to run local dependency audits or git history secret checks.