ctf-web
Provides web exploitation techniques for CTF challenges. Use when the target is primarily an HTTP application, API, browser client, template engine, identity flow, or smart-contract frontend/backend surface, including XSS, SQLi, SSTI, SSRF, XXE, JWT, auth bypass, file upload, request smuggling, OAuth/OIDC, SAML, prototype pollution, and similar web bugs. Do not use it for native binary memory corruption, reverse engineering of standalone executables, disk or memory forensics, or pure cryptanalysis unless the web flaw is still the main path to the flag.
71
88%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Critical
Do not install without reviewing
Security
4 findings: 2 critical severity, 2 high severity. Installing this skill is not recommended: please review these findings carefully if you do intend to do so.
E005: Suspicious download URL detected in skill instructions.
What this means
Detected a suspicious URL in the skill instructions that could lead the agent to download and execute malicious scripts or binaries. This includes links to executables from untrusted sources, typosquatting of official packages, URL shorteners that obscure the destination, and personal file hosting services.
Why it was flagged
Yes — several URLs point to attacker-controlled hosts, cloud functions/webhook endpoints, or direct executable/shared-object/shell script filenames (untrusted personal hosting and direct .so/.sh links), which are high-risk vectors for distributing malware or staging exploitation.
E006: Malicious code pattern detected in skill scripts.
What this means
Detected high-risk code patterns in the skill content — including its prompts, tool definitions, and resources — such as data exfiltration, backdoors, remote code execution, credential theft, system compromise, supply chain attacks, and obfuscation techniques.
Why it was flagged
The content is an explicit offensive CTF playbook containing numerous step-by-step examples for credential harvesting, data exfiltration (webhook/attacker callbacks), remote code execution, SSRF/local file reads, and other active exploitation techniques — it functions as a malicious toolkit if used against real targets.
W007: Insecure credential handling detected in skill instructions.
What this means
The skill handles credentials insecurely by requiring the agent to include secret values verbatim in its generated output. This exposes credentials in the agent’s context and conversation history, creating a risk of data exfiltration.
Why it was flagged
The skill shows shell commands that require inserting JWTs/cookies/token strings verbatim into command-line tools (e.g., echo '<token>' ... and flask-unsign --cookie '<cookie>'), which would force an agent to handle and output secret values directly.
W008: Secret detected in skill content (API keys, tokens, passwords).
What this means
Detected sensitive credentials directly embedded within the skill content, such as API keys, access tokens, private keys, or service-specific secrets. Secrets should never be hardcoded in plain text within skill instructions.
Why it was flagged
I scanned the documentation for high-entropy, literal credentials. I flagged one high-entropy password that appears to be a real, usable credential (not a placeholder or truncated value): DB_PASSWORD='0NYa6PBH52y86C' found in the WordPress/RevSlider example. This string is random-looking and used as a concrete password in a mysql command — it meets the "secret" definition. Ignored potential / low-risk matches: - Truncated public key snippet "MIIBIjANBgkq..." in auth-jwt.md — truncated with "..." so treated as redacted/example. - Token placeholders like "eyJ..." and "token" or "<token>" — placeholders, not full secrets. - Simple/example passwords and markers such as "adminsession", "anything", "letmein", "YOUR_ID", "YOUR_API_KEY" — these are low-entropy or explicit placeholders and are intentionally ignored per rules.
- Repository
- ljagiello/ctf-skills
- Path
ctf-web/SKILL.md
- Commit
d19f35f
- Audited
- Security analysis
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.