Security Issue

DevOps & Security

security-issue

Security Issue is an Agent Skill for devops & security published in the xrplevm/node repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Create a security finding in the private peersyst/security repo with proper labels and format. Use when reporting a security vulnerability, concern, or observation found during audits or ad-hoc review.

View on GitHub ↗

QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

Open your project in Codex.
Copy and paste the prompt below.
Review files and risks before approving any action.

Prompt to paste

Inspect the Agent Skill at https://github.com/xrplevm/node/blob/HEAD/.claude/skills/security-issue/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/security-issue, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

Security Issue Skill

Create a security finding in peersyst/security. Gather the following information from the user or from context:

Severity: One of critical, high, medium, low, info
Area: The focus area (e.g., POA module, Authorization & access control, EVM integration, IBC & cross-chain, etc.)
Title: Short description of the finding
Location: File path and line numbers
Finding: Description of the vulnerability or concern
Impact: What could go wrong and under what conditions
Recommendation: Suggested fix or mitigation
Evidence: Code snippets, reasoning, or proof of concept (optional)

If any required field is missing, ask the user before proceeding.

Before creating

Check for duplicates first:

gh issue list -R peersyst/security --label "repo:xrplevm/node" --state all --json number,title,labels,state -q '.[] | select(.title | test("KEYWORD"; "i"))'

Replace KEYWORD with a relevant term from the title. If a duplicate exists, inform the user and ask whether to proceed.

Create the issue

gh issue create -R peersyst/security \
  --title "[SEVERITY_UPPER] Title here" \
  --label "repo:xrplevm/node,SEVERITY,pending" \
  --body "$(cat <<'EOF'
## Area

<focus area>

## Finding

<finding description>

## Location

<file:line>

## Impact

<impact description>

## Recommendation

<recommendation>

## Evidence

<code snippets or reasoning>
EOF
)"

After creating

Report the issue URL back to the user.