2.6k
GitHub Stars
2
Bundled Files
2 months ago
Catalog Refreshed
4 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstrat where the catalogue uses aiagentskills.
npx veilstrat add skill openclaw/skills --skill ralph-security- _meta.json470 B
- SKILL.md6.6 KB
Overview
This skill performs a comprehensive, evidence-driven security audit across 100 focused iterations (~30–60 minutes). It balances depth and speed to surface critical findings across OWASP Top 10, authentication, secrets, infrastructure, and code quality. The output is a reproducible per-iteration log and a final consolidated report for triage and remediation.
How this skill works
The auditor runs a deterministic 100-iteration loop where each iteration executes one specific check, verifies the finding against code and libraries, and records a structured result. Every 10 iterations the tool saves progress to a report file; at completion it generates a final scorecard and prioritized recommendations. The process enforces single-check iterations, evidence-first verification, and clear severity/confidence levels.
When to use it
- Weekly security check for active projects
- New project onboarding to baseline security posture
- Pre-release audit before major deployments
- When asked: 'security audit', 'ralph security', or 'audit this project'
- To regularly validate OWASP Top 10 and infrastructure controls
Best practices
- Run against a recent, synced clone of the repo and include CI/CD manifests
- Provide environment samples (.env.example) or CI variables for accurate verification
- Run with --resume when interrupted to avoid duplicated work
- Triage NEEDS_REVIEW findings by inspecting the referenced code or libraries
- Save and version the generated .ralph-report.md for audit trails
Example use cases
- Automated weekly scan in CI to detect newly introduced vulnerabilities
- Security review during sprint handoff for a new microservice
- Pre-release checklist to catch auth, secrets, and TLS regressions
- Onboarding security baseline for archived or forked repositories
- Targeted focus runs (e.g., --focus=secrets or --phase=4) to validate specific risk areas
FAQ
A full 100-iteration audit typically takes 30–60 minutes depending on repo size and environment checks.
Can I run fewer iterations?
Yes — the --iterations parameter accepts 1–200. Partial runs still follow the one-check-per-iteration discipline.
What if a finding is inconclusive?
Inconclusive results are marked NEEDS_REVIEW rather than FAIL so a human can verify code, library usage, or DB constraints.