file-upload
Skill1 starsChanged 3 months agoMITView on GitHub
This is a thin human-facing router. Use skill.yaml as the source of truth for exact commands, inputs, outputs, and workflow chaining.
15 other projects use a version of this.
Adopted by
Most recently taken up by
- mahumadad/quarrytheir own version, first seen Nov 8, 2026
- SubhiSec/claude-ai-cyber-security-skillstheir own version, first seen Oct 25, 2026
- Dhruv2mars/skillstheir own version, first seen Oct 20, 2026
- FlyelepAI/agent-skillstheir own version, first seen Oct 17, 2026
- fusebase-dev/fusebase-flowtheir own version, first seen Oct 16, 2026
- TaiMaBenJi/taima-skillstheir own version, first seen Oct 11, 2026
Used with
Projects with it also use ssti, oauth-oidc and 6 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
SubhiSecSkillssti
Hunt Server-Side Template Injection (SSTI) in Jinja2, Twig, Freemarker, Velocity, Smarty, ERB, Handlebars, Mustache, and Spring (SpEL). Use when input is reflected in a way that suggests template rendering — error pages, email templates, PDF generators, dynamic content systems.
Also in 6 projects that use this
SubhiSecSkilloauth-oidc
Hunt OAuth 2.0 and OIDC flaws — redirect_uri abuse, state CSRF, PKCE bypass, scope manipulation, implicit-flow token theft, postMessage origin tricks, ID token sub claim swap, JWKS confusion, response_type confusion, and OAuth-CSRF. Use when an app has Google/GitHub/Facebook/Apple/custom OAuth or OpenID Connect.
Also in 3 projects that use this
yaklangSkillopen-redirect
Open redirect playbook. Use when URL parameters, form actions, or JavaScript sinks control navigation targets and may redirect users to attacker-controlled destinations.
Also in 6 projects that use this
langbyyiSkillcsrf
CSRF testing playbook. Use when reviewing state-changing web flows, anti-CSRF defenses, SameSite behavior, JSON CSRF, login CSRF, and OAuth state handling.
Also in 4 projects that use this
langbyyiSkillpath-traversal
Path traversal and LFI playbook. Use when file paths, download endpoints, include operations, archive extraction, or wrapper behavior may expose filesystem control.
Also in 4 projects that use this
zebbernSkilljs-analysis
Analyze JavaScript files to discover hidden endpoints, API keys, secrets, and sensitive data. Use when testing web applications, when user mentions JavaScript analysis, or when looking for hidden API endpoints.
Also in 3 projects that use this
- +1 more from SubhiSec
- +1 more from langbyyi
Other versions15 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 15
- cdxiaodong/cain-agent★ 953same name
- Rain-kl/OpenFlare★ 298same name
- SubhiSec/claude-ai-cyber-security-skills★ 45same name
- 0xGhostCAT/claude-ai-cyber-security-skills★ 41same name
- thejefflarson/soundcheck★ 20same name
- fusebase-dev/fusebase-flow★ 9same name
- FlyelepAI/agent-skills★ 4same name
- iAskShahram/skills★ 4same name
- langbyyi/websec-skills★ 4same name
- Dhruv2mars/skills★ 3same name
5 more not listed
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 repository50 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .claude/CLAUDE.mdCLAUDE.md
- CLAUDE.mdCLAUDE.md
- agent-safetySkill
- ai-llmSkill
- apiSkill
- asset-graphSkill
- authSkill
- auto-researchSkill
- binary-analysisSkill
- business-logicSkill
- campaignSkill
- cicd-securitySkill
- cloudSkill
- cors-csrfSkill
- coverageSkill
- cross-accountSkill
- domain-modelSkill
- enrichmentSkill
- evaluation-harnessSkill
- graphql-auditSkill
- http-protocolSkill
- identity-domainSkill
- impact-verifierSkill
- meme-coin-auditSkill
- mobileSkill
- modern-browserSkill
- nuclei-scannerSkill
- oob-infraSkill
- osintSkill
- personaSkill
- plannerSkill
- privescSkill
- program-memorySkill
- race-conditionSkill
- rceSkill
- reconSkill
- reportingSkill
- sastSkill
- scope-managerSkill
- skill-scientistSkill
- sqliSkill
- ssrfSkill
- standard-catalogSkill
- technique-kbSkill
- traffic-corpusSkill
- triage-validationSkill
- vuln-intelSkill
- web3-auditSkill
- xssSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 1 is distinctive, and 2 are very specific to this project.
0
Common
Most of the 11 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 16
Start with upload-fuzz unless prior evidence points to a more specific workflow.
- Very specific: line 17
Follow each workflow next mapping in skill.yaml after reviewing generated findings.
- Distinctive: line 18
If a workflow has no script reference, treat it as a manual or tool-native workflow and use the closest phase runbook when available.
“Common” is measured: kept by at least 6 in 10 of the 11 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
File Upload
Overview
File upload vulnerabilities — extension bypass, content-type spoofing, magic byte bypass, path traversal, polyglot files, SVG injection
This is a thin human-facing router. Use skill.yaml as the source of truth for exact commands, inputs, outputs, and workflow chaining.
Quick Reference
- Skill:
file-upload - Severity range:
medium,high,critical - Required tools:
curl,ffuf,python3,nuclei,playwright,openssl - Expected input files:
all_urls.txt - Scope check: confirm authorization before running intrusive or authenticated testing.
Workflow Selection
- Start with
upload-fuzzunless prior evidence points to a more specific workflow. - Follow each workflow
nextmapping inskill.yamlafter reviewing generated findings. - If a workflow has no script reference, treat it as a manual or tool-native workflow and use the closest phase runbook when available.
- Runbooks: use
runbooks/and select the closest phase runbook when workflow names do not map 1:1.
Available Workflows
| Workflow | Purpose | Script paths | Primary outputs | Evidence |
upload-fuzz | Fuzz a known upload endpoint with extension, magic-byte, and MIME variants. | .claude/skills/file-upload/scripts/upload_fuzzer.py | $OUTDIR/file-upload/fuzz/findings.jsonl | $OUTDIR/file-upload/fuzz/evidence/ |
svg-payloads | Generate SVG XSS, XXE, and SSRF payload files for manual upload testing. | .claude/skills/file-upload/scripts/svg_xxe_generator.py | $OUTDIR/file-upload/svg/findings.jsonl<br>$OUTDIR/file-upload/svg/ | $OUTDIR/file-upload/svg/evidence/ |
polyglot-payload | Generate one polyglot file with an operator-supplied payload string. | .claude/skills/file-upload/scripts/polyglot_factory.py | $OUTDIR/file-upload/polyglot/payload.* | $OUTDIR/file-upload/polyglot/evidence/ |
Evidence Required
- Save raw request and response data for each confirmed finding.
- Include timestamps, affected target, exact workflow name, tool versions, and reproduction steps.
- Store screenshots or terminal captures in the workflow evidence directory when the workflow defines one.
- Evidence templates from
skill.yaml: webshell_access: Curl response showing PHP shell command executionsvg_xss: Playwright screenshot showing SVG script alert popuptraversal_write: ls output showing file written outside uploads dir
References
- Source of truth:
skill.yaml - Runbooks:
runbooks/ - OWASP WSTG:
WSTG-BUSL-08
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.

