File Path Traversal Testing Agent Skill

This skill should be used when the user asks to "test for directory traversal", "exploit path traversal vulnerabilities", "read arbitrary files through web applications", "find LFI vulnerabilities", or "access files outside web root". It provides comprehensive file path traversal attack and testing methodologies.

3k tokens

context cost

the whole folder, loaded on every use

files

instructions only

copies elsewhere

how many repositories repackaged it

505

stars on the repo

on the repository, not the skill itself

Install

one command, takes just this skill from the repository

npx skills add https://github.com/Dokhacgiakhoa/Agent-Skills-4-Vibe-Coding-CLI --skill File Path Traversal Testing

What comes with it

10 945 bytes besides the instruction

sub-skills/application-restrictions.md

sub-skills/common-payloads.md

sub-skills/encoding-variants.md

sub-skills/permission-restrictions.md

sub-skills/phase-1-understanding-path-traversal.md

sub-skills/phase-10-prevention-measures.md

sub-skills/phase-2-identifying-traversal-points.md

sub-skills/phase-3-basic-exploitation-techniques.md

sub-skills/phase-4-bypass-techniques.md

sub-skills/phase-5-linux-target-files.md

sub-skills/phase-6-windows-target-files.md

sub-skills/phase-7-automated-testing.md

sub-skills/phase-8-lfi-to-rce-escalation.md

sub-skills/phase-9-testing-methodology.md

sub-skills/required-knowledge.md

sub-skills/required-tools.md

sub-skills/target-files.md

sub-skills/testing-considerations.md

The instruction itself

22 sections, as written by the author

File Path Traversal Testing

Purpose

Identify and exploit file path traversal (directory traversal) vulnerabilities that allow attackers to read arbitrary files on the server, potentially including sensitive configuration files, credentials, and source code. This vulnerability occurs when user-controllable input is passed to filesystem APIs without proper validation.

Prerequisites

🧠 Knowledge Modules (Fractal Skills)

1. Required Tools

2. Required Knowledge

3. Phase 1: Understanding Path Traversal

4. Phase 2: Identifying Traversal Points

5. Phase 3: Basic Exploitation Techniques

6. Phase 4: Bypass Techniques

7. Phase 5: Linux Target Files

8. Phase 6: Windows Target Files

9. Phase 7: Automated Testing

10. Phase 8: LFI to RCE Escalation

11. Phase 9: Testing Methodology

12. Phase 10: Prevention Measures

13. Common Payloads

14. Target Files

15. Encoding Variants

16. Permission Restrictions

17. Application Restrictions

18. Testing Considerations

Other skills for the same job

different authors, same section of the catalogue

Webapp Testing

by anthropics

vendor ×12

Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.

6k tokens scripts

Finishing A Development Branch

by ZhanlinCui

×7

Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup

1k tokens

Test Driven Development

by w95

×7

Use when implementing any feature or bugfix, before writing implementation code

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes

10k tokens scripts

Verification Before Completion

by ZhanlinCui

×6

Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always

Expert guidance for systematic backtesting of trading strategies. Use when developing, testing, stress-testing, or validating quantitative trading strategies. Covers "beating ideas to death" methodology, parameter robustness testing, slippage modeling, bias prevention, and interpreting backtest results. Applicable when user asks about backtesting, strategy validation, robustness testing, avoiding overfitting, or systematic trading development.

Cloud laboratory platform for automated protein testing and validation. Use when designing proteins and needing experimental validation including binding assays, expression testing, thermostability measurements, enzyme activity assays, or protein sequence optimization. Also use for submitting experiments via API, tracking experiment status, downloading results, optimizing protein sequences for better expression using computational tools (NetSolP, SoluProt, SolubleMPNN, ESM), or managing protein design workflows with wet-lab validation.

This skill should be used for time series machine learning tasks including classification, regression, clustering, forecasting, anomaly detection, segmentation, and similarity search. Use when working with temporal data, sequential patterns, or time-indexed observations requiring specialized algorithms beyond standard ML approaches. Particularly suited for univariate and multivariate time series analysis with scikit-learn compatible APIs.

19k tokens

How to use it

Copy the folder

Take dokhacgiakhoa/file path traversal testing from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.