agentleFS
Sign inStart free
JustineDevsJustineDevs/premortem/.agents/skills/injection-checking/SKILL.md

injection-checking

Skill2 starsChanged 5 months agoApache-2.0View on GitHub

Entry P1 category router for injection testing. Use when routing between XSS, SQLi, SSRF, XXE, SSTI, command injection, and NoSQL injection workflows based on how attacker-controlled input is consumed.

2 other projects use a version of this, 1 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    After confirming this is an injection-class issue, use it to decide whether it is mainly browser context, database, template engine, …

    line 13

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Injection Testing Router

This is the routing entry point when input reaches a dangerous interpreter or execution environment.

After confirming this is an injection-class issue, use it to decide whether it is mainly browser context, database, template engine, server-side requests, XML parsing, or system commands.

When to Use

  • Input reaches HTML, JS, SQL, templates, URL fetchers, XML parsers, or shell
  • You have not yet decided whether to start with XSS, SQLi, SSRF, XXE, SSTI, CMDi, or NoSQL
  • You need to choose the correct deep-topic skill based on input flow

Skill Map

  • XSS Cross Site Scripting
  • SQLi SQL Injection
  • SSRF Server Side Request Forgery
  • XXE XML External Entity
  • SSTI Server Side Template Injection
  • CMDi Command Injection
  • NoSQL Injection
  • Deserialization Insecure
  • JNDI Injection
  • Expression Language Injection
  • CRLF Injection
  • Extra Injection Types (SSI, LDAP, XPath)
  • Request Smuggling
  • Prototype Pollution
  • Type Juggling
  • HTTP Parameter Pollution
  • XSLT Injection
  • CSV Formula Injection

Recommended Flow

  1. First identify the final sink of the input
  2. Then choose the topic skill that best matches that interpreter
  3. Small payload samples and quick triage are merged into each main skill; no extra payload router is needed

Related Categories

  • file-access-vuln

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free