dirien/yet-another-agent-harness / .claude/skills/security-audit
security-audit
UnverifiedComprehensive security audit covering OWASP Top 10, secrets detection, supply chain security, threat modeling, and language-specific vulnerability patterns. Investigates actual code paths rather than grep-matching keywords. Generates a scored SECURITY_AUDIT.md with prioritized remediation. Use when assessing application security, preparing for a security review, or onboarding to a codebase with security concerns.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 5.7 KB |
| references/language-security.md | markdown | 3.8 KB |
| references/owasp-patterns.md | markdown | 4.5 KB |
| references/report-template.md | markdown | 3.1 KB |
| references/secrets-and-supply-chain.md | markdown | 2.9 KB |
| references/threat-model.md | markdown | 3.6 KB |
references/report-template.md
View on GitHub<!-- Copyright 2025-2026 Richard Shade. Licensed under Apache-2.0. -->
<!-- SPDX-License-Identifier: Apache-2.0 -->
# Security audit report template
Use this structure when generating SECURITY_AUDIT.md.
## Template
```markdown
# Security Audit Report
Generated: YYYY-MM-DD
Scope: [full codebase / specific module / recent changes]
Tools used: [list tools that ran successfully]
Tools unavailable: [list tools that were missing]
## Executive Summary
| Severity | Count |
| -------- | ----- |
| CRITICAL | X |
| HIGH | X |
| MEDIUM | X |
| LOW | X |
Overall risk assessment: [brief 1-2 sentence summary]
## Findings
### [SEVERITY] Finding title
- **Category**: [OWASP A0X / Secrets / Supply Chain / Language-specific]
- **File**: `path/to/file.ext:line`
- **Evidence**: [what was found, why it is a vulnerability, and how
it could be exploited]
- **Mitigations present**: [any existing protections, or "none"]
- **Remediation**: [specific action to fix, with code example if
applicable]
- **Effort**: [S/M/L]
[Repeat for each finding, ordered by severity then effort]
## Threat Model Summary
### Entry Points Assessed
| Entry Point | Type | Auth Required | Threats Identified |
| ----------- | ---- | ------------- | ------------------ |
| ... | ... | ... | ... |
### Key STRIDE Findings
| Threat | Category | DREAD Score | Severity |
| ------ | -------- | ----------- | -------- |
| ... | ... | ... | ... |
## Supply Chain Assessment
| Check | Status | Details |
| ----- | ------ | ------- |
| Lockfile committed | ... | ... |
| Dependency vulnerabilities | ... | ... |
| Dependency confusion risk | ... | ... |
| Stale dependencies | ... | ... |
## Remediation Priority
### Immediate (CRITICAL)
- [ ] [Action with file:line and specific fix]
### This Sprint (HIGH)
- [ ] [Action with file:line and specific fix]
### Next Sprint (MEDIUM)
- [ ] [Action with file:line and specific fix]
### Backlog (LOW)
- [ ] [Action with file:line and specific fix]
## Recommendations
### Quick Wins (high impact, low effort)
[List items that can be fixed in < 1 day with significant
security improvement]
### Infrastructure Improvements
[Tooling, CI/CD, monitoring recommendations]
### Process Improvements
[Code review checklists, dependency update cadence, security
training]
```
## Severity assignment guide
| Severity | Criteria | Example |
| -------- | -------- | ------- |
| CRITICAL | Exploitable now, data breach or RCE risk | Hardcoded API key in git history |
| HIGH | Exploitable with moderate effort | SQL injection in admin endpoint |
| MEDIUM | Requires specific conditions | Missing rate limiting on login |
| LOW | Theoretical risk, minimal impact | Debug logging includes request IDs |
## Report quality checklist
Before finalizing the report, verify:
- Every finding has a specific file:line reference
- Every finding has concrete remediation (not just "fix this")
- False positives from automated tools have been filtered out
- Severity assignments are consistent across findings
- The remediation priority section has actionable items
- Quick wins are called out separately for immediate impact
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |