SKILLEMALL.ai

AC HTML Injection Testing

This skill should be used when the user asks to "test for HTML injection", "inject HTML into web pages", "perform HTML injection attacks", "deface web applications", or "test content injection vulnerabilities". It provides comprehensive HTML injection attack techniques and testing methodologies.

modbender/skill-library-mcp Agent Skills author: modbender MIT 1 file body ≈ 3 163 tokens Open the sourcegithub.com analyzed 2 d ago

This skill should be used when the user asks to "test for HTML injection", "inject HTML into web pages", "perform HTML injection attacks", "deface web…

As a process C 60/100 · Has gaps — weak spots: result and completion, consistency, progress reporting

ProcedureSoftware developmentSecuritytype and topics are labelled automatically from the skill text
JSON
Technical rating
A
94/100
safety, quality, tests
Safety 60%
100
Quality 40%
84
Run on models
none yet
Process rating
C
60/100
Has gaps
Result and completion w 14
0
Progress reporting w 2
0
Consistency w 8
40
the three weakest of ten parameters · all ten

The same skill appears in 1 more place: RA-Skills

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 · 0

    ✓ No critical or high findings

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

    Against the Agent Skills spec

    • warning name-format name should be kebab-case (lowercase letters, digits, hyphens)

    Process rating: all ten parameters 60/100

    • 0Result and completion. Does not say what the result is
    • 0Progress reporting. Says nothing while it works
    • 40Consistency. Frontmatter name (HTML Injection Testing) differs from the folder (html-injection-testing)
    • 50Failures and branches. 0 branches, has a failure section
    • 60Tools and files. Uses tools (web) that frontmatter does not declare
    • 70When it triggers. States when to use, but not when not to
    • 70Inputs and preconditions. Inputs and preconditions are listed
    • 100Steps. 35 steps
    • 100Execution cost. Instruction body is 3163 tokens
    • 100Running it twice. Mutating operations check current state

    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

    • +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
    • +5Description quotes 5 example trigger phrases
    • +3Description length 296: enough signal without eating the budget
    • +4Structure: 37 headings
    • +3Step-by-step instructions: 35 items
    • +4Has examples (23 code blocks)

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