From kodo
Verify OWASP compliance and security patterns. Use when reviewing code for security vulnerabilities, checking for injection, or auditing tool usage.
How this skill is triggered — by the user, by Claude, or both
Slash command
/kodo:security-checkThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
When reviewing code for security, verify the following areas systematically.
When reviewing code for security, verify the following areas systematically.
Check that external content is scanned before processing:
UserPromptSubmit hook (blocks at score >= 4)createMemCell() injection checkVerify sensitive path blocking covers:
.env, .env.* files.ssh/* (keys, config, known_hosts)isSensitivePath() and isConfidentialContent() in src/security/blocklist.tsVerify shell commands are classified correctly:
rm -rf /, mkfs, dd if=, format commandspython -c, node -e, docker run, PowerShell -enc, eval(), exec()classifyShellRisk() in src/security/policy.tsVerify LLM output scanning covers:
<script>, javascript: URIs, event handlers (onload=, onerror=)eval(), Function(), import(), child_processDROP TABLE, DELETE FROM, UNION SELECTrm -rf /src/security/output-guard.tsVerify memory system is tamper-resistant:
computeChecksum()verifyChecksum() detects tamperingloadMemCells() validates JSON with isMemCell() type guardVerify cryptographic operations:
timingSafeEqual with hex validationnpx claudepluginhub yannabadie/kodoclawEnforces security best practices and vulnerability prevention: input validation, authentication, secrets management, OWASP top 10. Activated by security, auth, vulnerability, injection, XSS, CSRF, rate-limit keywords.
Audits code security using OWASP Top 10 checklists for input validation, auth/authz, API security, data protection, and logging. Use for secure implementations and vulnerability reviews.
Provides CDSS development patterns for drug interaction checking, dose validation, clinical scoring (NEWS2, qSOFA), and alert classification integrated into EMR workflows.