framework-laravel

Complete the following steps in exact order.

Updated Jul 30, 2026
One-click install
npx skills add https://github.com/salmanabdurrahman/pi-pentest-agent --skill framework-laravel
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: framework-laravel
Source: https://github.com/salmanabdurrahman/pi-pentest-agent/tree/main/skills/framework-laravel
Command: npx skills add https://github.com/salmanabdurrahman/pi-pentest-agent --skill framework-laravel

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill addresses the risk of misconfigured Laravel applications by automating the detection of common security vulnerabilities and exposure points in production environments.

Core Features & Use Cases

  • Configuration Audit: Identifies exposed .env files, debug mode leaks, and insecure session or CSRF settings.
  • Surface Exposure Detection: Scans for unauthorized access to debugging tools like Telescope, Ignition, and Horizon.
  • Use Case: Use this skill during a security assessment to quickly verify if a Laravel application has properly disabled development-only tools and protected sensitive environment variables before moving to deeper testing.

Quick Start

Use the framework-laravel skill to perform a read-only security review of the target application at the provided URL.

Frequently Asked Questions about framework-laravel

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

FAQPage Schema
How do I audit a Laravel web application for security misconfigurations?

A Laravel security audit detects misconfigurations by scanning for exposed .env files, debug mode leaks, and unauthorized access to administrative dashboards or development tools like Telescope and Ignition.

What does exposed debug mode leak in Laravel production environments?

Exposed debug mode in Laravel production environments leaks sensitive environment variables and application stack traces, which occurs when development-only debugging tools like Ignition and Telescope remain accessible to unauthorized users.

Can I use an automated security review to detect Laravel .env file exposure?

Yes, an automated security review detects Laravel .env file exposure by performing read-only configuration audits to verify if sensitive environment variables are properly protected before deeper testing.

How do I check if Laravel development tools like Horizon are disabled in production?

Check if Laravel development tools like Horizon are disabled in production by running an automated surface exposure detection scan that verifies administrative dashboards and debugging interfaces are inaccessible.

Are there limitations to automated Laravel security posture reviews?

Limitations of automated Laravel security posture reviews include the exclusion of destructive payload execution and credential testing, restricting the assessment to read-only configuration and surface exposure validation only.