Security
Run focused Laravel security checks for authorization, request forgery, rate limits, uploads, secrets, APIs, and configuration.From its SKILL.md
npx -y skills add soden46/syarif-laravel-ai-skills --skill securityAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 3 stars3 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
2.7 KB, 492 tokens by cl100k_base, as published. Nobody here has run it
Security
Run a focused security pass whenever work touches authentication, authorization, input handling, uploads, external integrations, payment-like flows, public APIs, or sensitive data.
Access Control
Every route/action that reads or mutates protected data needs authorization.
Use:
- route middleware for coarse access boundaries;
- Policies for model actions;
- Gates for cross-cutting checks;
- Form Request
authorize()for request-input-dependent checks.
Test both allowed and denied paths.
Request Forgery And Rate Limits
Use CSRF protection for browser forms. Exclude webhooks only deliberately, and authenticate webhook requests through signatures, shared secrets, IP allowlists, or provider verification as appropriate.
Apply rate limits to abuse-prone routes such as login, password reset, public forms, file uploads, and expensive API endpoints.
Input And Output Safety
Validate all request input at the boundary. Use query builder bindings or Eloquent instead of interpolated raw SQL.
Escape output in Blade. Be deliberate about HTML rendering.
For frontend stacks, expose only the props needed by the page. Do not send hidden sensitive data because it is "not displayed."
Uploads And Files
Validate uploaded files for:
- required/optional state;
- MIME/type;
- extension if relevant;
- size;
- count;
- image dimensions when needed.
Store files through Laravel Storage. Do not trust original filenames for storage paths. Keep visibility explicit.
Secrets And Logs
Keep credentials in environment/config, not database-backed admin settings or source files.
Do not log:
- tokens;
- signatures;
- passwords;
- card data;
- full provider payloads;
- unnecessary personally identifiable information.
Use structured logs with safe identifiers and sanitized summaries.
Log::info('integration.gateway.create.completed', [
'record_id' => $record->id,
'reference' => $record->public_reference,
'provider_status' => $response->status(),
]);
API Security
For APIs:
- return consistent errors;
- hide stack traces;
- validate input;
- authorize every action;
- apply rate limits;
- avoid leaking internal IDs when public identifiers are needed;
- add compatibility tests for consumed response shapes.
Dependency And Configuration Review
When dependency or deployment configuration changes are in scope:
- check for known advisories;
- remove unused packages;
- avoid exposing frontend env values that are not meant for browsers;
- verify production debug settings are safe.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.
Gives 0 of the 12 instructions most security skills give in 492 tokens
Counted across 666 of the 889 authors here whose files we hold, read 2026-09-06
- Use parameterized queries for database accessin 82 of 666, across 79 files
- Hash passwords with BCryptin 55 of 666, across 39 files
- Implement rate limiting for public endpointsin 48 of 666, across 34 files
- Use environment variables for secretsin 35 of 666
- Scan dependencies for vulnerabilitiesin 35 of 666, across 24 files
- Validate and sanitize all user inputin 35 of 666, across 32 files
- Add security headers to all responsesin 34 of 666, across 20 files
- Validate all external input at the system boundaryin 26 of 666, across 25 files
- Use parameterized queries to prevent SQL injectionin 25 of 666, across 13 files
- Store secrets in Vault or environment variablesin 25 of 666, across 10 files
- Run containers as a non-root userin 21 of 666, across 18 files
- Validate all input using Bean Validationin 19 of 666, across 5 files
Said here and by no other author read
- Authorize every route reading or mutating protected data
- Use route middleware for coarse access boundaries
- Use Policies for model actions
- Use Gates for cross-cutting checks
- Use Form Request authorize for input-dependent checks
- Test both allowed and denied paths
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.