agentleFS
Sign inStart free
MysterionRiseMysterionRise/ctf-kit/skills/web/SKILL.md

web

Skill12 starsChanged 9 months agoMITView on GitHub

Solve CTF web security challenges: SQL injection, XSS, authentication bypass, SSTI, path traversal, and source code audit. Use when given a URL, web app source code, or HTTP traffic. Triggers: .php .html .js files, "SQL injection", "XSS", "SSTI", "LFI", "RFI", "cookie", "JWT", "robots.txt", "directory enumeration", http:// or https:// targets. Tools: sqlmap, gobuster, ffuf, nikto, burpsuite. NOT for network packet analysis (use forensics).

12 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

6 rules. 0 are common, 5 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 11 edited versions we read keep these.

  • 5

    Distinctive

    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
  1. Distinctive:

    Use this command for challenges involving:

    line 19
  2. Distinctive:

    Look for .git, .svn, backup files

    line 60
  3. Distinctive:

    Test input fields for injection

    line 61
  4. Very specific:

    When using /ctf-kit:team-solve with a web challenge, the lead spawns 3 specialists.

    line 77
  5. Distinctive:

    All web teammates require plan approval: before sending requests to the target.

    line 79
  6. Distinctive:

    Before any teammate sends a request to the target:

    line 96

“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

CTF Web

Analyze and solve web security challenges.

When to Use

Use this command for challenges involving:

  • Web applications
  • SQL injection
  • XSS vulnerabilities
  • Authentication bypass
  • API exploitation
  • Source code analysis

Bundled Scripts

  • check-tools.sh — Verify required web tools are installed
  • run-gobuster.sh — Directory enumeration with structured output. Outputs JSON with accessible paths, redirects, and forbidden paths.

Instructions

  1. First check tool availability: bash scripts/check-tools.sh

  2. For directory/file enumeration (outputs structured JSON):

    bash scripts/run-gobuster.sh http://target.com
bash scripts/run-gobuster.sh http://target.com /path/to/wordlist.txt
bash scripts/run-gobuster.sh http://target.com /path/to/wordlist.txt php,html,txt

    JSON output includes:

    • accessible: paths returning 200 (with size)
    • redirects: paths returning 3xx
    • forbidden: paths returning 403 (may indicate hidden content)
    • suggestions: which paths to investigate

  3. For SQL injection:

    sqlmap -u "http://target.com/page?id=1" --dbs
sqlmap -u "http://target.com/page?id=1" -D database -T table --dump
  4. Manual testing checklist:
    • Check robots.txt, sitemap.xml
    • Look for .git, .svn, backup files
    • Test input fields for injection
    • Examine cookies and headers
    • View page source

Common Vulnerabilities

VulnerabilityTest Payload
SQL Injection' OR '1'='1
XSS<script>alert(1)</script>
Path Traversal../../../etc/passwd
SSTI{{7*7}} or ${7*7}
Command Injection; id or | id

Team Roles

When using /ctf-kit:team-solve with a web challenge, the lead spawns 3 specialists.

All web teammates require plan approval before sending requests to the target.

RoleTeammate NameFocusToolsFirst Action
Recon & Enumerationweb-reconDirectory scanning, technology fingerprinting, hidden paths, backup files, robots.txt, source code reviewgobuster, ffuf, scripts/run-gobuster.sh, curlCheck robots.txt, run gobuster, view page source, identify tech stack
Injectioninjection-testerSQLi, XSS, SSTI, command injection, path traversal, SSRF, deserializationsqlmap, manual payloads, curlMap input fields, test with common payloads from the patterns table above
Auth & Logicauth-analystJWT manipulation, session handling, IDOR, privilege escalation, business logic flaws, API abusejwt_tool, curl, burpInspect cookies/tokens, test auth bypass, enumerate API endpoints

When to broadcast

  • Recon: "Found admin panel at /admin" or "Technology: Flask with Jinja2 (SSTI likely)" — injection tester focuses there
  • Injection: "SQLi confirmed on parameter X, dumping DB" — auth analyst checks for stored creds
  • Auth: "JWT uses none algorithm" or "IDOR on user ID" — others test with escalated access
  • Any: "Found the flag" — immediate broadcast, all stop

Plan approval flow

Before any teammate sends a request to the target:

  1. Teammate describes what they want to do and why
  2. Lead reviews for safety (no destructive actions, rate limiting)
  3. Lead approves or redirects

Example Usage

/ctf-kit:web ./webapp-source/
/ctf-kit:web http://challenge.ctf.com

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.

Check your setup, free