agentleFS
Sign inStart free
willianbswillianbs/skills/security-auditor/SKILL.md

security-auditor

Skill0 starsChanged 4 months agoMITView on GitHub

Threat-aware security assessment of code and trust boundaries with evidence-based findings. Use for auth, PII, payments, integrations, or when review escalates. Emits SECURITY_REPORT. Never invents vulns, never prints live secrets, and never claims exploitability without a proof sketch for High+.

54 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use proofreader, refactoring-guide and 10 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.
  • xcrrrSkill

    proofreader

    Use this skill when reviewing written content for grammar, spelling, punctuation, style consistency, and tone—before publishing, submitting, or sending. Trigger phrases: 'proofread this', 'check my writing', 'review this for errors', 'edit this email/report/essay'. Do NOT use when structural rewrites or content changes are needed—proofreading fixes surface errors, not substantive problems.

    Also in 3 projects that use this

  • peopleforresterSkill

    refactoring-guide

    Safe refactoring patterns and techniques. Use when the user wants to improve code structure, reduce duplication, or make code more maintainable without changing behavior. Emphasizes incremental changes with test coverage.

    Also in 3 projects that use this

  • zwjbendnSkill

    habit-builder

    Designs and manages healthy habits for sustainable weight loss through lifestyle change. Uses Atomic Habits / Tiny Habits methodology — small behaviors that compound over time. Use this skill when: the system needs to recommend a new habit after onboarding, a current habit graduates or fails, the user asks about building habits, or Weekly Review identifies a behavioral pattern worth addressing. Also use when evaluating habit progress, deciding when a habit has "graduated," or handling a restart after the user falls off. This skill does not send its own reminders — habit check-ins are woven into meal conversations managed by Notification Composer. This skill owns the check-in logic (when, how often, tone); Notification Composer provides the conversation vehicle.

    Also in 3 projects that use this

  • juanlurgSkill

    sql-optimizer

    Analyzes SQL queries and generates an optimization report notebook with explanations, identified issues, and rewritten queries. Use when the user wants to optimize, explain, improve, or debug a SQL query, or mentions query performance, slow queries, or SQL optimization.

    Also in 3 projects that use this

  • belokonmSkill

    data-scientist

    Expert in statistical analysis, predictive modeling, machine learning, and data storytelling to drive business insights.

    Also in 3 projects that use this

  • glinckerSkill

    qa-engineer

    QA specialist agent for test planning, execution, and regression analysis

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

5 rules. 0 are common, 4 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 47 edited versions we read keep these.

  • 4

    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:

    Do not implement fixes unless asked.

    line 46
  2. Distinctive:

    Never invent CVEs or vulns for drama.

    line 93
  3. Very specific:

    Never print tokens/passwords/keys.

    line 94
  4. Distinctive:

    Never equate “uses crypto” with “secure.”

    line 95
  5. Distinctive:

    Never skip authz negative cases on access-control changes.

    line 96

“Common” is measured: kept by at least 6 in 10 of the 47 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

Purpose

Find real security risk before production. Prioritize by Likelihood × Impact with evidence.

When to Use / When NOT to Use

Use when: authz/authn, PII, payments, file uploads, SSRF-prone integrations, dependency/supply-chain concerns, HighRisk specs, quality-gate missing security evidence.

Do not use when: pure UI copy; style review; user wants a full pen-test simulation without codebase access.

Preconditions

Code/architecture context available. Prefer CONTEXT_PACK + diff/IMPL_REPORT.

Inputs / Outputs

Inputs: change set or system scope, CONTEXT_PACK, data classification if known.

Outputs: SECURITY_REPORT (authoritative for quality-gate security section).

Upstream / Downstream

Upstream: threat-modeler (preferred for HighRisk), code-reviewer, feature-implementer, engineering-os, quality-gate.

Downstream: feature-implementer (remediation), quality-gate, adr-enforcer (security architecture).

Core Principles

  1. Assets and trust boundaries before checklists.
  2. Least privilege, validate inputs, fail closed.
  3. Likelihood × Impact; reachability matters.
  4. High+ needs a proof sketch (data flow / exploit path).
  5. Redact secrets; report leaks without echoing values.
  6. Business-logic abuse cases count.
  7. Do not implement fixes unless asked.

Process

  1. Assets — data, sessions, keys, admin actions, money movement.
  2. Trust boundaries — client/server, services, tenants, admin vs user.
  3. Abuse cases — spoofing, tampering, repudiation, info disclosure, DoS, elevation (STRIDE-light).
  4. Review surfaces — authn/authz, injection, SSRF, XSS, CSRF, deserialization, uploads, secrets, deps, insecure defaults.
  5. Supply chain — new deps, install scripts, lockfile drift (note; don’t invent CVEs).
  6. Findings — severity, confidence, evidence, remediation, release impact.
  7. False-positive control — mark Low confidence when unreachability likely.

Evidence Requirements

High/Critical: data-flow or concrete code path. Never paste secret values—only locations.

Stop Conditions / Failure Modes

ConditionAction
Critical exploitable issueBlock release
Insufficient context for HighRisk areaProceedWithConditions or Block until context loaded
Suspected secret in repoCritical finding + redact

Severity + Confidence

Critical = authz bypass, RCE, mass data leak, auth break with proven/high-confidence path.

Output Contract

## SECURITY_REPORT
Assets & boundaries: ...
Findings:
  - Severity, Confidence, evidence, remediation
Release impact: Proceed | ProceedWithConditions | Block
Decision: ...

Handoffs

  • quality-gate — consume as authoritative security section
  • feature-implementer — remediations
  • adr-enforcer — security architecture decisions

Never

  • Never invent CVEs or vulns for drama.
  • Never print tokens/passwords/keys.
  • Never equate “uses crypto” with “secure.”
  • Never skip authz negative cases on access-control changes.

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