SKILLEMALL.ai

AC hunt-lfi

Hunt Local File Inclusion (LFI), Remote File Inclusion (RFI), and Path Traversal — /etc/passwd read, log poisoning → RCE, PHP filter-chain RCE (no upload needed), php:// / data:// / zip:// / phar:// wrappers, RFI via allow_url_include, directory traversal read/write/delete. Covers OOB/blind LFI confirmation and false-positive discipline. Use when hunting file-include or path-traversal bugs on any target.

elementalsouls/Claude-BugHunter Agent Skills author: elementalsouls 1 file body ≈ 4 053 tokens Open the sourcegithub.com analyzed 2 h ago

Hunt Local File Inclusion (LFI), Remote File Inclusion (RFI), and Path Traversal — /etc/passwd read, log poisoning → RCE, PHP filter-chain RCE (no upload…

As a process C 51/100 · Has gaps — weak spots: result and completion, when it triggers, failures and branches

ProcedureSoftware developmentInfrastructureSecuritytype and topics are labelled automatically from the skill text
JSON
Technical rating
A
92/100
safety, quality, tests
Safety 60%
98
Quality 40%
82
Run on models
none yet
Process rating
C
51/100
Has gaps
Result and completion w 14
0
Failures and branches w 10
0
When it triggers w 12
20
the three weakest of ten parameters · all ten

How to improve

    For the model run — optional
    • Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
    • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

    Guard findings · 2

    ✓ No critical or high findings

    Medium and low: 2
    • low Secrets in code secret-high-entropy-token SKILL.md:127
      High-entropy token-like string (may be an id, hash or a credential)
      ?file=data://text/plain;base64,PD9w…Oz8+&c=id   # <?php system($_GET['c']);?>

    A further 1 matches are quotations in this security skill's documentation and are not counted as findings.

    Files scanned: 1. Evidence is masked. Grey chips explain why severity was lowered.

    Against the Agent Skills spec

    • note frontmatter-key unknown frontmatter key "sources"
    • note frontmatter-key unknown frontmatter key "report_count"
    • note edit-residue the text marks something as outdated (lines 84, 132, 218): check that old rules are not kept next to new ones — the full check reads the text for contradictions

    Process rating: all ten parameters 51/100

    • 0Result and completion. Does not say what the result is
    • 0Failures and branches. Linear process with no failure handling
    • 20When it triggers. No condition that starts the skill
    • 30Running it twice. 3 mutating operations with no state check
    • 60Tools and files. Uses tools (bash, web, python) that frontmatter does not declare
    • 70Inputs and preconditions. Inputs and preconditions are listed
    • 70Execution cost. Instruction body is 4053 tokens
    • 100Steps. 35 steps
    • 100Consistency. Name and required fields are in place
    • 100Progress reporting. Reports progress
    • low The response is described with custom markup (6 tags): a typed call is more reliable

    Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

    Quality signals

    • +5Description has no quoted example phrases that should trigger the skill
    • +4Description does not say when NOT to use the skill (false activations)
    • +3Output format is not stated: the model decides each time
    • +1No license
    • +2Single-language instructions
    • +3Description length 407: enough signal without eating the budget
    • +4Structure: 25 headings
    • +3Step-by-step instructions: 35 items
    • +4Has examples (12 code blocks)

    Quality base 70; lint remarks subtract, signals add up to 100. Result: 82.