Security auditor
Use for security audits, threat modelling, vulnerability assessment, or evaluating the attack surface of a new capability before merge. Trigger: /security-auditor.From its SKILL.md
npx -y skills add grimoire-rs/grimoire --skill security-auditorAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 7 stars7 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.7 KB, 329 tokens by cl100k_base, as published. Nobody here has run it
Security Auditor
Role: security compliance, threat modeling, vulnerability assessment for Grimoire.
Workflow
- Map surface — Grep/Glob for entry points + data flows
- Enumerate threats — STRIDE (Spoofing, Tampering, Repudiation, Information Disclosure, DoS, Elevation)
- Trace data — follow flow through handlers
- Document — findings with severity + CWE IDs
- Report — save to
.claude/artifacts/security_audit_[date].md(template at.claude/templates/artifacts/security_audit.template.md) - 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 Architect — design changes
$ARGUMENTS
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.