web-app
Skill159 starsChanged 52 days agoMITView on GitHub
Web application testing: injection and client-side flaws.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- angelgabrieljacintohuayllasco/clipboard-skillstheir own version, first seen Sep 20, 2026
- kekurttel/pentest-skillstheir own version, first seen Aug 3, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- kekurttel/pentest-skills★ 4same name
- angelgabrieljacintohuayllasco/clipboard-skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository7 other files it gives its agents.
- AGENTS.mdAGENTS.md
- api-testingSkill
- business-logicSkill
- identity-authSkill
- llm-securitySkill
- misconfigSkill
- pentestSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 2 are distinctive, and 1 is 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.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 22
Do not use for authorization/session flaws, API protocol coverage, or workflow abuse.
- Very specific: line 44
Run target-touching checks only through the authorized Violin execution tools.
- Distinctive: line 45
Read the matched playbook's stop conditions before validation.
≈ “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
Web Application Security Testing
On-demand skill for web application input-validation and client-side vulnerability classes. The pentest orchestrator routes here when a discovered surface matches one class below. Load only the matched playbook with read_file; do not eagerly load every playbook.
When to Use
- A web route, parameter, body field, upload, parser, template, or client-side sink is in scope.
- Recon identifies an injection sink, unsafe deserialization, XML parser, or JavaScript object merge.
- Do not use for authorization/session flaws, API protocol coverage, or workflow abuse; use the routed specialist skill.
Playbook Routing
| Class | Playbook |
| SQL Injection | playbooks/sqli.md |
| Cross-Site Scripting | playbooks/xss.md |
| Command Injection | playbooks/command-injection.md |
| Server-Side Request Forgery | playbooks/ssrf.md |
| Path Traversal / LFI | playbooks/path-traversal.md |
| Server-Side Template Injection | playbooks/ssti.md |
| XXE / XML Entity Injection | playbooks/xxe.md |
| NoSQL Injection | playbooks/nosql-injection.md |
| LDAP Injection | playbooks/ldap-injection.md |
| XPath Injection | playbooks/xpath-injection.md |
| Prototype Pollution | playbooks/prototype-pollution.md |
| Insecure Deserialization | playbooks/deserialization.md |
| Improper Input Validation | playbooks/input-validation.md |
Common Pitfalls
- Run target-touching checks only through the authorized Violin execution tools.
- Read the matched playbook's stop conditions before validation.
- Store redacted proof under
$ENG_DIR/evidence/exploitation/<class>/.
Verification Checklist
- Engagement bootstrap and scope validation succeeded.
- The matched playbook alone was loaded and bound to the PTT task.
- Evidence captures the baseline and the decisive differential response.
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.