agentleFS
sp1esp1e/claude-skills/skill-security-auditor/SKILL.md

skill-security-auditor

Skill1 starsChanged 31 days agoMITView on GitHub

Security audit and vulnerability scanning for AI agent skills before install. Detects prompt injection, dangerous code, exfiltration, credential harvesting, and supply chain risks. Use when evaluating untrusted skills or gating installs.

  • Reads credentials

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

3 rules. 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 20 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Before the audit, confirm these inputs.

    line 41
  2. Distinctive:

    Stop rule: ask only the 2-3 that most change the output.

    line 47
  3. Very specific:

    All tools take a target (file or directory), and support --strict (any HIGH → FAIL) and --json.

    line 57

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

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

Skill Security Auditor

Scan and audit AI agent skills for security risks before installation. Performs static analysis on code files for dangerous patterns, scans markdown files for prompt injection, validates dependency supply chains, checks file system boundaries, and detects obfuscation. Produces a structured PASS / WARN / FAIL verdict with findings categorized by severity and actionable remediation guidance.

Keywords: skill security, AI security, prompt injection, code audit, supply chain, dependency scanning, data exfiltration, credential harvesting, obfuscation detection, pre-install security

Core Capabilities

  • Code execution risk detection — command injection (os.system, subprocess shell=True, backticks), eval/exec/compile, obfuscation (base64/hex/chr()), network exfiltration, credential harvesting (~/.ssh, ~/.aws), privilege escalation.
  • Prompt injection detection — system-prompt overrides, role hijacking, safety bypass, hidden zero-width/HTML-comment instructions, data-extraction directives, excessive-permission requests.
  • Supply chain analysis — known-vulnerable pins, typosquatting, unpinned versions, inline pip/npm install, low-reputation packages.
  • File system & structure validation — out-of-scope paths, hidden/credential files, unexpected binaries, escaping symlinks, oversized payloads.
  • Verdict & reporting — PASS / WARN / FAIL with severity-categorized findings, remediation, and a strict mode for CI gates.

When to Use

  • Evaluating a skill from an untrusted source before installation
  • Pre-install security gate for CI/CD pipelines
  • Auditing a skill directory or git repository for malicious code
  • Reviewing skills before adding them to a team's approved list
  • Post-incident scanning of installed skills

Clarify First

Before the audit, confirm these inputs. If any is unknown or vague, ASK — do not assume:

  • Target path — the skill file or directory to scan (the subject of every scanner)
  • Scan dimensions — code execution / prompt injection / supply chain (selects which of the three scanners run)
  • Strict mode / gate threshold — whether any HIGH finding forces FAIL (CI gate vs advisory report changes the verdict)

Stop rule: ask only the 2-3 that most change the output. If the user says "just draft it," proceed and list your assumptions at the top of the artifact.

Tools

ToolPurposeCommand
code_scanner.pyScan Python scripts for eval/exec, subprocess, network exfiltration, credential harvesting, obfuscation, unsafe importspython scripts/code_scanner.py <target> --strict --json
prompt_injection_scanner.pyScan markdown/text for prompt-injection patterns and hidden directivespython scripts/prompt_injection_scanner.py <target> --strict --json
supply_chain_checker.pyCheck imports/requirements for typosquatting, unpinned versions, inline installspython scripts/supply_chain_checker.py <target> --strict --json

All tools take a target (file or directory), and support --strict (any HIGH → FAIL) and --json.

References

Load the reference that matches the task — keep this file lean and pull detail on demand:

  • references/threat-model-and-patterns.md — the attack-vector threat model, trust boundaries, full regex pattern sets for code-execution and prompt-injection detection, and known evasion techniques. Read when deciding what to scan for or tuning detection.
  • references/audit-output-and-workflow.md — the report format, verdict criteria (incl. strict mode), CI/CD integration YAML, and the manual audit checklist. Read when producing or interpreting an audit.
  • references/quality-and-best-practices.md — static-analysis limitations, common pitfalls, best practices, troubleshooting matrix, and success criteria. Read before shipping or relying on an audit.

Scope & Limitations

This skill covers:

  • Static pattern-based detection of dangerous code constructs in Python, Bash, JavaScript, and TypeScript files
  • Prompt injection scanning across all markdown files within a skill package
  • Dependency supply chain validation for requirements.txt and package.json
  • File structure boundary checks including symlinks, binaries, hidden files, and oversized payloads

This skill does NOT cover:

  • Runtime or dynamic analysis — code is never executed during the audit (see skill-tester for runtime validation)
  • Live CVE database lookups or real-time vulnerability feeds (see dependency-auditor for active CVE scanning)
  • Infrastructure-level security controls such as network segmentation, container hardening, or cloud IAM policies (see infrastructure-compliance-auditor in ra-qm-team)
  • Compliance framework certification against ISO 27001, SOC 2, GDPR, or other regulatory standards (see information-security-manager-iso27001 and gdpr-dsgvo-expert in ra-qm-team)

Integration Points

SkillIntegrationData Flow
dependency-auditorFeed audit findings into live CVE scanning for flagged dependenciesSecurity audit report → dependency-auditor for real-time vulnerability lookup
ci-cd-pipeline-builderEmbed the audit workflow as a required check in generated CI/CD pipelinesPipeline template ← audit job YAML from this skill's CI/CD section
skill-testerRun dynamic runtime tests on skills that pass static analysisPASS verdict from this skill → skill-tester for behavioral validation
infrastructure-compliance-auditorExtend auditing scope from skill-level to infrastructure-level security controlsSkill audit findings → infrastructure auditor for environment-wide posture review
env-secrets-managerCross-reference credential harvesting findings with secrets management policyCredential-access flags from audit → env-secrets-manager for policy verification
pr-review-expertSurface audit findings as inline PR review comments on flagged linesAudit report line references → PR review annotations for developer visibility

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.