security-scan

Reviews codebase security design and audits code for injection, secrets, and crypto flaws.

3|1|Updated Aug 26, 2026
One-click install
npx skills add https://github.com/zeljkoobrenovic/sokrates-skills --skill security-scan-zeljkoobrenovic
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: security-scan
Source: https://github.com/zeljkoobrenovic/sokrates-skills/tree/main/skills/scanners/security-scan
Command: npx skills add https://github.com/zeljkoobrenovic/sokrates-skills --skill security-scan-zeljkoobrenovic

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Security reviews of a codebase are slow and inconsistent: design-level questions (how identity, permissions, and secrets are handled) get mixed up with line-level pattern hunting, and grep hits turn into false-positive noise. This Skill performs a structured security review in one pass, producing verifiable, severity-calibrated findings with cited evidence. ## Core Features & Use Cases - Design-first review: Reconstructs identity/access, secrets handling, input validation, and third-party trust from actual enforcement points, recording defaults and bypass surfaces. - Disciplined code audit: Sweeps for in-tree credentials, injection sinks (command/SQL/path/template), crypto and randomness fitness, unsafe/FFI/dynamic code, and plugin or update trust — every grep hit is verified for reachability and mitigation before it becomes a finding. - Posture synthesis: Emits one summary finding stating the security design, the worst confirmed issue, what was swept clean, and what was not covered. - Use Case: Point it at a repository with a Sokrates _sokrates analysis and ask for a security audit; it writes _sokrates/reports/ai-insights/security-scan.json, validates it, and renders an interactive HTML explorer of the findings. ## Quick Start Run a security review of this repository using the existing Sokrates analysis and show me the worst confirmed findings and the overall security posture.

Frequently Asked Questions about security-scan

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run a security review of a codebase with AI?

Run the security-scan skill against a repository that has a Sokrates _sokrates analysis folder. It maps the security design from enforcement points first, then audits code for concrete flaws, and writes validated findings to _sokrates/reports/ai-insights/security-scan.json.

How does this security scan avoid false positives?

Every pattern match is treated as a candidate, not a finding. Before reporting, the scan checks whether attacker-influenced data can actually reach the line and what mitigation already exists; mitigated or unreachable patterns are reported as info or folded into a clean verdict.

Does the security scan check dependencies for CVEs?

No. It has no vulnerability database, so it never guesses CVE status. Instead it reports the dependency trust mechanisms present, such as lockfiles, cargo-deny, npm audit, Dependabot, and vendored patches, under the third-party-trust group.

What security areas does the scan cover?

Eight groups: identity and access design, secrets at rest and in the tree, input validation at trust boundaries, injection sinks, cryptography and randomness, unsafe/FFI/dynamic code, third-party runtime trust, and a final posture summary with coverage statement.

When should I use architecture-scan instead of security-scan?

Use architecture-scan's security-boundaries group for the structure of trust: where untrusted data enters, sandbox and privilege boundaries, and escape hatches. Security-scan reads that map first and judges what crosses those boundaries and how crossings are checked.