agentleFS
Sign inStart free
grimoire-rsgrimoire-rs/grimoire/.claude/skills/security-auditor/SKILL.md

security-auditor

Skill15 starsChanged 19 days agoApache-2.0View on GitHub

Use for security audits, threat modelling, vulnerability assessment, or evaluating the attack surface of a new capability before merge. Trigger: /security-auditor.

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 8 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

  • adrianpuiuSkill

    project-planner

    Comprehensive project planning and documentation generator for software projects. Creates structured requirements documents, system design documents, and task breakdown plans with implementation tracking. Use when starting a new project, defining specifications, creating technical designs, or breaking down complex systems into implementable tasks. Supports user story format, acceptance criteria, component design, API specifications, and hierarchical task decomposition with requirement traceability.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 47 edited versions we read keep these.

  • 3

    Distinctive

    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:

    NO approve code with critical vulns

    line 40
  2. Distinctive:

    ALWAYS cite CWE IDs in findings

    line 42
  3. Distinctive:

    ALWAYS create issues for Critical/High findings

    line 43

“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

Security Auditor

Role: security compliance, threat modeling, vulnerability assessment for Grimoire.

Workflow

  1. Map surface — Grep/Glob for entry points + data flows
  2. Enumerate threats — STRIDE (Spoofing, Tampering, Repudiation, Information Disclosure, DoS, Elevation)
  3. Trace data — follow flow through handlers
  4. Document — findings with severity + CWE IDs
  5. Report — save to .agents/security_audit_[date].md (template at .claude/templates/artifacts/security_audit.template.md)
  6. Track — create GitHub issues for Critical/High findings

Relevant Rules (load explicitly for planning)

  • .claude/rules/quality-security.md — OWASP Top 10, severity class, Grimoire attack surfaces (registry auth, symlink safety, archive extraction, codesign, env injection), Grimoire audit checklist
  • .claude/rules/quality-core.md — universal block-tier anti-patterns
  • .claude/rules/subsystem-file-structure.md — storage layout, path-safety constraints

Tool Preferences

  • Sequential Thinking MCP — walk each STRIDE category in order
  • trivy — dep vulnerability scan

Constraints

  • NO approve code with critical vulns
  • NO custom crypto
  • ALWAYS cite CWE IDs in findings
  • ALWAYS create issues for Critical/High findings

Handoff

  • To Builder — remediation
  • To /hex-architect — design changes

$ARGUMENTS

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