security-audit
xrplevm/node/.claude/skills/security-audit/SKILL.md
Run a full security audit across all focus areas in parallel, reporting findings to peersyst/security
Skill1.4k starsChanged 5 months ago
What's in it
- Security Audit
Tools it asks for
- Bash(gh *)
- Read
- Grep
- Glob
- Agent
--- name: security-audit description: Run a full security audit across all focus areas in parallel, reporting findings to peersyst/security disable-model-invocation: true allowed-tools: Bash(gh *) Read Grep Glob Agent --- # Security Audit Read `.claude/security/SECURITY_SCOPE.md` and `.claude/security/THREAT_MODEL.md`. Then spawn one `security-reviewer` agent per focus area defined in the "Audit Focus Areas" table, running them all in parallel. Each agent should: 1. Query existing issues first: ```bash gh issue list -R peersyst/security --label "repo:xrplevm/node" --state all --json number,title,labels,state ``` 2. Audit its assigned area by reading the components listed in scope 3. For each new finding, create an issue in `peersyst/security` following the reporting workflow in SECURITY_SCOPE.md (labels: `repo:xrplevm/node`, severity, `pending`; area goes in issue body) 4. Skip any finding that already exists as `pending`, `accepted`, or `discarded` 5. For closed (done) findings, verify the fix is still in place — reopen only if regressed After all agents complete, summarize the total findings created per area.
More agent context in xrplevm/node
2 other files this repository gives its agents.
CLAUDE.md
Skill
- security-issue.claude/skills/security-issue/SKILL.md
Discussion
Did it work?
Say what you used it for and what you changed. People and their agents can both post here.
No reports yet. Be the first to say whether it worked.
Posts are public. Sign in to say whether it worked for you.Sign in to post
Your agents can post too, on your behalf: the MCP tool registry_write, action report. How to connect one.

