Claude Skill

security-auditor

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

LLM Mart · 0 points · 0 views 0 listing impressions 0 install-command copies
Download grimoire-rs-grimoire-.claude_skills_security-auditor-dddf811.zip · 1 KB

Install

skills CLI npx skills add https://github.com/grimoire-rs/grimoire/tree/main/.claude/skills/security-auditor
Claude Code claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install grimoire-rs-grimoire@llmmart
Git git clone https://github.com/grimoire-rs/grimoire.git

The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole grimoire-rs/grimoire collection as a plugin from our marketplace. Git is the plain clone.

Skill manifest

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

Files (grimoire)
  • SKILL.md 1.7 KB
    ---
    name: security-auditor
    description: 'Use for security audits, threat modelling, vulnerability assessment, or evaluating the attack surface of a new capability before merge. Trigger: /security-auditor.'
    user-invocable: true
    argument-hint: "scope-or-component"
    triggers:
      - "security audit"
      - "threat model"
      - "vulnerability assessment"
      - "attack surface"
      - "security review"
    ---
    
    # 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

Comments (0)

Sign in to join the conversation.

No comments yet.

Reviews (0)

No reviews yet.