web-app-sec
Skill1 starsChanged 5 days agoMITView on GitHub
Secure coding checklist for web apps: access control, XSS/CSRF, SSRF, injection, uploads, JWT, headers, API security. Use when writing or reviewing code that handles auth, user input, files, sessions, or external requests, or when the user asks for a security scan or audit.
In this repository23 other files it gives its agents.
- AGENTS.mdAGENTS.md
- broSkill
- create-my-skillSkill
- glassmorphismSkill
- swiftui-designSkill
- humanizerSkill
- ponytail-auditSkill
- ponytail-debtSkill
- ponytail-gainSkill
- ponytail-helpSkill
- ponytail-reviewSkill
- ponytailSkill
- clean-up-git-historySkill
- commit-msgSkill
- diagnoseSkill
- fixSkill
- grill-meSkill
- implementSkill
- loopSkill
- subagentsSkill
- update-docsSkill
- verify-appSkill
- sudo-ssh-authSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 15
When unsure, choose the more restrictive option.
- Distinctive: line 19
Read only the reference files relevant to the code at hand.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
<!-- Changed from https://github.com/BehiSecc/VibeSec-Skill. Apache License 2.0; see LICENSE. -->Secure Coding Guide for Web Applications
Approach code as a bug hunter and make it as secure as possible without breaking functionality.
- Fail closed: when a check errors out, deny access.
- Authentication and authorization on every endpoint, not just at routing.
- Validate input server-side; encode output for its context.
- When unsure, choose the more restrictive option.
Topic router
Read only the reference files relevant to the code at hand. For a full audit or scan, read all of them.
| Topic | Reference | Read when |
| Access control | references/access-control.md | Code decides who can read or change a resource (ownership, IDs, roles, sessions, tenants) |
| XSS, CSRF, client secrets, open redirect, passwords | references/client-side.md | Code renders user input, changes state from the browser, redirects, or handles passwords or secrets |
| SSRF, file upload, SQL injection, XXE, path traversal | references/server-side.md | Code fetches URLs, accepts files, builds queries, parses XML, or uses user input in paths |
| Security headers, JWT, mass assignment, GraphQL | references/headers-jwt-api.md | Code sets response headers, issues or verifies JWTs, binds request bodies, or exposes GraphQL |
| Command injection, deserialization, CORS, rate limits, races, webhooks, sessions, secrets, dependencies | references/misc.md | Code runs commands, parses serialized data, sets CORS, handles payments or webhooks, manages sessions, or ships config and dependencies |
Audit output
When asked for a review or scan, report findings ranked Critical, High, Medium, Low. For each one give: file and line, what an attacker can do in one sentence, a minimal fix. Say which topics were checked and which were not. Report only issues you traced to real code paths; do not list generic advice. When writing new code, apply the rules silently and mention only the non-obvious choices.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.