SKILLEMALL.ai

BC templates

View-layer lens: stored and reflected XSS in server-rendered templates of every dialect (Jinja2 |safe / autoescape false / safe_columns, Django mark_safe, Handlebars {{{ }}}, ERB raw / html_safe, Thymeleaf th:utext, JSP <%= %>, Vue v-html, React dangerouslySetInnerHTML, Razor @Html.Raw, Go text/template), context-confusion bugs in href / src / onclick / <script> interpolations, SSTI from runtime-built template source, template-layer information disclosure, and state-changing forms rendered with no CSRF token. Activate whenever the repo holds templates/, views/, *.html, *.j2, *.erb, *.hbs, *.jsp, *.cshtml, *.vue, or a render_template / render / res.render call.

visa/visa-vulnerability-agentic-harness Agent Skills author: visa 2 files · 1 script body ≈ 1 705 tokens Open the sourcegithub.com↗ analyzed 6 d ago

View-layer lens: stored and reflected XSS in server-rendered templates of every dialect (Jinja2 |safe / autoescape false / safecolumns, Django marksafe…

As a process C 52/100 · Has gaps — weak spots: result and completion, inputs and preconditions, failures and branches

TemplateSoftware developmentData and analyticstype and topics are labelled automatically from the skill text
JSON
Technical rating
B
92/100
safety, quality, tests
Safety 60%
100
Quality 40%
80
Run on models
none yet
Process rating
C
52/100
Has gaps
Result and completion w 14
0
Inputs and preconditions w 11
0
Failures and branches w 10
0
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 · 0

    ✓ No critical or high findings

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

    Against the Agent Skills spec

    ✓ No remarks against the Agent Skills spec

    Process rating: all ten parameters 52/100

    • 0Result and completion. Does not say what the result is
    • 0Inputs and preconditions. Does not say what the process needs to start
    • 0Failures and branches. Linear process with no failure handling
    • 0Progress reporting. Says nothing while it works
    • 60Tools and files. Uses tools (bash, web) that frontmatter does not declare
    • 70When it triggers. States when to use, but not when not to
    • 100Steps. 25 steps
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 1705 tokens
    • 100Running it twice. No mutating operations
    • 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
    • +4No input/output examples
    • +1No license
    • +2Single-language instructions
    • +3Description length 668: enough signal without eating the budget
    • +4Structure: 9 headings
    • +3Step-by-step instructions: 25 items

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