security

Identify and fix one security vulnerability per session using SAST and DAST/fuzzing.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/ericklemos/ai-tools --skill security-ericklemos
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: security
Source: https://github.com/ericklemos/ai-tools/tree/main/.agents/skills/security
Command: npx skills add https://github.com/ericklemos/ai-tools --skill security-ericklemos

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Finds and fixes one meaningful security issue per session through both static analysis (SAST) and dynamic testing (DAST/fuzzing).

Core Features & Use Cases

  • Performs iterative security analysis to identify meaningful vulnerabilities and validate fixes within a single session.
  • Combines static and dynamic testing to cover code-level weaknesses and runtime behavior.
  • Fits into development and security workflows for vulnerability remediation and secure-by-default deployments.

Quick Start

Identify and fix one meaningful security vulnerability in the codebase using static analysis (SAST) and dynamic testing (DAST/fuzzing).

Frequently Asked Questions about security

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

FAQPage Schema
How do I find and fix security vulnerabilities in my code during a session?

Static analysis (SAST) scans source code to find code-level weaknesses like input validation flaws or secrets exposure, while dynamic testing (DAST) and fuzzing evaluate runtime behavior to uncover exploitable vulnerabilities.

Can I integrate SAST and DAST testing into my existing code review workflows?

This approach handles input validation, secrets exposure, and JWT manipulation by combining static analysis (SAST) and dynamic testing (DAST/fuzzing) to cover both code-level weaknesses and runtime behavior.

What is the best way to automate vulnerability remediation for secure deployments?

This approach handles input validation, secrets exposure, and JWT manipulation by combining static analysis (SAST) and dynamic testing (DAST/fuzzing) to cover both code-level weaknesses and runtime behavior.

Do I need a specific environment setup to run fuzzing and dynamic application security testing?

This approach handles input validation, secrets exposure, and JWT manipulation by combining static analysis (SAST) and dynamic testing (DAST/fuzzing) to cover both code-level weaknesses and runtime behavior.

Why does this security analysis focus on fixing only one vulnerability per session?

This approach handles input validation, secrets exposure, and JWT manipulation by combining static analysis (SAST) and dynamic testing (DAST/fuzzing) to cover both code-level weaknesses and runtime behavior.