More screenshots
Works with the AI Agents you already use
Laravel Config Check
APP_DEBUG=true on a live Laravel site shows your database password and API keys on the error page, and a .env copy left in public_html is downloaded by bots within hours.
$5
Laravel Config Check
Example session with this skill installed
Check this project with laravel-config-check.
- Read your context and instructions
- Compiled the laravel config check
$ python3 scripts/check_laravel.py examples/risky
BLOCK .env.production:4 L02 WEAK_OR_HARDCODED_APP_KEY
APP_KEY=<redacted, 16 chars> is a sample value or too short
Why: APP_KEY is a known sample value, too short, or written into config/app.php. Laravel signs and encrypts cookies, sessions and encrypted data with it, so anyone who knows it can forge them; on older Laravel versions a forged cookie can run code on the server.
Safer: Run php artisan key:generate on each server, keep the key only in the server's .env or secret store, and use 'key' => env('APP_KEY') in config/app.php. Rotate a key that was committed.
BLOCK .env.production:5 L01 DEBUG_IN_PRODUCTION
BLOCK config/app.php:6 L01 DEBUG_IN_PRODUCTION
BLOCK config/database.php:11 L03 SECRET_IN_CONFIG
BLOCK public/.env.backup L04 ENV_FILE_IN_WEB_ROOT
REVIEW .env.production:6 L15 HTTP_APP_URL
REVIEW .env.production:9 L14 DEBUG_LOG_LEVEL
REVIEW .env.production:14 L16 WEAK_DATABASE_LOGIN
REVIEW .env.production:18 L11 INSECURE_SESSION_COOKIE
REVIEW .env.production:19 L13 DEBUG_TOOLS_IN_PRODUCTION
REVIEW .env.production:20 L17 LOW_BCRYPT_ROUNDS
REVIEW config/cors.php:8 L12 CORS_ANY_ORIGIN_WITH_CREDENTIALS
(Each finding also has Why and Safer lines, as in the first one.)
Verdict: BLOCK. Checked 5 files, 5 with Laravel config content.
This is a static check of file text. NOT FLAGGED is not a guarantee.
Connects securely to your tools. The creator never sees your data.
About this skill
APP_DEBUG=true on a live Laravel site shows your database password and API keys on the error page, and a .env copy left in public_html is downloaded by bots within hours. This skill finds those and nine other Laravel configuration mistakes before you deploy, and tells you how to fix each one.
Your agent runs a scanner on your project: every .env file (.env, .env.production, backup copies; examples and templates are skipped) and every config/*.php file. It reads .env files the way Laravel does (quotes, export, comments, the last value wins) and reads PHP config arrays with their comments, strings and env('NAME', default) fallbacks. Local and testing environments are read but not reported. It never runs PHP or artisan. It returns BLOCK, REVIEW, or NOT FLAGGED, with the file, line, reason, and a safer approach. Keys and passwords are never printed.
What it checks
BLOCK
- L01: APP_DEBUG on in production, or true as the default in config/app.php
- L02: APP_KEY that is a sample value, too short, or written into config/app.php
- L03: a password, secret or API key written into a config file or an env() default
- L04: a .env file or copy inside public/, public_html/ or another web root folder
REVIEW
- L11: session cookie not secure, or readable by JavaScript
- L12: CORS allowing every origin with supports_credentials
- L13: Telescope or Debugbar on in production
- L14: LOG_LEVEL=debug in production
- L15: an http:// APP_URL
- L16: the root database user or an empty database password
- L17: BCRYPT_ROUNDS below 10
What's included
- The scanner (Python 3.9+, standard library only)
- A rules guide with the reason and safer approach for each rule
- A risky and a safe example project (.env.production and config files), a .env copy in public/ to find, and the real report the scanner produces on the risky example
Limits It reads files as written, so values from the server's real environment, config:cache and code in service providers are not seen, and it cannot see a web server whose document root is the whole project folder. NOT FLAGGED is not a guarantee.
Static check of .env and config files. The real server environment, cached config and service-provider code are not seen. NOT FLAGGED is not a guarantee.
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
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 5 days ago
Permissions
Runs one local Python script in the terminal. It reads your project's files, writes nothing, and makes no network calls. The example files include clearly fake, inert values (SomeRandomString, not-a-real-password) for the scanner to find.