agentleFS
zyphr-labszyphr-labs/bounty-harness/.claude/skills/file-upload/SKILL.md

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

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.
  • SubhiSecSkill

    ssti

    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

  • SubhiSecSkill

    oauth-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

  • yaklangSkill

    open-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

  • langbyyiSkill

    csrf

    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

  • langbyyiSkill

    path-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

  • zebbernSkill

    js-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

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
  1. Very specific:

    Start with upload-fuzz unless prior evidence points to a more specific workflow.

    line 16
  2. Very specific:

    Follow each workflow next mapping in skill.yaml after reviewing generated findings.

    line 17
  3. Distinctive:

    If a workflow has no script reference, treat it as a manual or tool-native workflow and use the closest phase runbook when available.

    line 18

“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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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-fuzz unless prior evidence points to a more specific workflow.
  • Follow each workflow next mapping in skill.yaml after 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

WorkflowPurposeScript pathsPrimary outputsEvidence
upload-fuzzFuzz 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-payloadsGenerate 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-payloadGenerate 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 execution
  • svg_xss: Playwright screenshot showing SVG script alert popup
  • traversal_write: ls output showing file written outside uploads dir

References

  • Source of truth: skill.yaml
  • Runbooks: runbooks/
  • OWASP WSTG: WSTG-BUSL-08

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.