Skip to content

Vinix24/vnx-orchestration / skills/security-engineer

security-engineer

Verified

SEOcrawler security vulnerability scanner and hardening specialist covering code analysis, dependency audits, and infrastructure review.

FileKindSize
SKILL.mdskill md3.9 KB
references/_MAPPING.mdmarkdown423 B
template.mdmarkdown1.8 KB

template.md

View on GitHub
# Security Engineer Report Template

## Output Location
Write your report to: `$VNX_DATA_DIR/unified_reports/`

## Filename Format
`{timestamp}-{track}-security-{title}.md`

Example: `20260202-143000-C-security-api-audit.md`

## Report Structure

### Summary
Brief overview of security assessment completed (2-3 sentences)

### Tags (Required)
- [tag1, tag2, tag3]  # Use specific, compound tags (e.g., sse-streaming, browser-pool, kvk-validation). Avoid general-only tags.

### Scope
- Components audited
- Attack surface assessed
- Methodology used (OWASP, static analysis, dynamic testing)

### Vulnerabilities Found
#### Critical
- CVSS 9.0+ findings with evidence

#### High
- CVSS 7.0-8.9 findings with evidence

#### Medium
- CVSS 4.0-6.9 findings

#### Low/Informational
- CVSS 0.1-3.9 findings and observations

### Remediation
- Fixes applied (with code references)
- Fixes recommended (with priority)
- Mitigations in place

### Evidence
- Scan output and tool results
- Proof-of-concept examples
- Dependency audit results
- Configuration review findings

### Open Items
<!-- List any unfinished work, blockers, or issues discovered -->
<!-- Format: - [ ] [severity] Title (optional details) -->
<!-- Severities: [blocker], [warn], [info] -->
<!-- Leave empty if all work completed -->

### Recommendations
- Security hardening priorities
- Monitoring and detection improvements
- Dependency update schedule
- Security testing to add to CI

### Intelligence Feedback
<!-- If your dispatch included [INTELLIGENCE_DATA] with offered_pattern_hashes, report which patterns you actually used: -->
used_pattern_hashes: []

## Quality Standards
- All findings include CVSS score
- Evidence for every vulnerability
- Remediation guidance for all critical/high
- No secrets or credentials in report
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: 472kUpdated Claude CodeCodexVerifiedInstall
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: 472kUpdated Claude CodeCodexVerifiedInstall
rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first.Stars: 194kUpdated Claude CodeCodexVerifiedInstall