agentleFS
abhijeetkakade1234abhijeetkakade1234/skills/redteam-attack/SKILL.md

redteam-attack

Skill2 starsChanged 16 days agoNo licenceView on GitHub

Red-team any codebase, system design, API spec, architecture document, smart contract, or technical document to find exploits, attack vectors, and vulnerabilities — then produce prioritised fixes with solutions. Use this skill whenever the user says "red team this", "find exploits", "break this", "attack plan", "security review", "vulnerability analysis", "how would someone abuse this", "stress test this", "what are the weaknesses", "find bugs", "hack this", "pen test", or uploads any code/spec/architecture and wants it attacked. Also trigger when a user asks how their system could be gamed, abused, bypassed, or manipulated. Works for ALL system types: web apps, APIs, smart contracts, protocols, CLI tools, databases, mobile apps, AI systems, SaaS platforms, distributed systems — any code or design document. Always produce a downloadable .docx report with attacks + solutions.

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 3 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

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

No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.

≈ “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.

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.