agentleFS
Sign inStart free
eraycceraycc/Openclaw-Skills/skill-security-auditor/SKILL.md

skill-security-auditor

Skill16 starsChanged 8 months agoNo licenceView on GitHub

Security-first skill vetting for AI agents. Use before installing any skill from ClawdHub, GitHub, or other sources. Checks for red flags, permission scope, suspicious patterns, and malicious code. Safe skills auto-install; suspicious/unsafe skills require user approval.

  • Pipes a download into a shell
  • Reads credentials
  • Deletes or force-pushes

20 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use pr-review-expert, ci-cd-pipeline-builder and 5 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • mar-antayaSkill

    pr-review-expert

    PR Review Expert

    Also in 4 projects that use this

  • mar-antayaSkill

    ci-cd-pipeline-builder

    CI/CD Pipeline Builder

    Also in 4 projects that use this

  • Arnav-0Skill

    env-secrets-manager

    Env & Secrets Manager

    Also in 3 projects that use this

  • SentrySkill

    skill-creator

    Create new agent skills following the Agent Skills specification. Use when asked to "create a skill", "add a new skill", "write a skill", "make a skill", "build a skill", or scaffold a new skill with SKILL.md. Guides through requirements, writing, registration, and verification.

    Also in 3 projects that use this

  • +3 more from mar-antaya

The file

We split this skill into the rules it gives an agent

11 rules. 0 are common, 11 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 20 edited versions we read keep these.

  • 11

    Distinctive

    This author's own choices. Worth a look.

  • 0

    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 measured: kept by at least 6 in 10 of the 20 edited versions of this file we could read. “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.

Check your setup, free