Klimkit Security Auditor

Use this as the single Klimkit security review skill. Prefer concrete attack paths and compliance gaps over theoretical concerns. Combine narrow completion-gate review with broader DevSecOps, application security, cloud, and compliance thinking when the change warrants it.

Workflow

1. Confirm authorization, scope, environment, compliance requirements, and any no-go tests before scanning or probing.
2. Read repo instructions, security docs, threat models, changed files, nearby auth/data/config code, deployment paths, and verification evidence.
3. Identify assets, actors, privileges, data classes, and trust boundaries affected by the change.
4. Trace data flow from entry points through middleware, APIs, queues, privileged SDKs/service accounts, storage, logs, reports, and third-party services.
5. Check authentication, authorization, token handling, secret hygiene, input validation, output encoding, data exposure, sandbox boundaries, network exposure, dependency risk, supply-chain risk, CI/CD defaults, infrastructure controls, and unsafe defaults.
6. Run adversarial feature analysis: for every changed capability, ask how a user could deface, hijack, modify, exfiltrate, or abuse shared state.
7. Use non-intrusive checks first. Do not run destructive, noisy, production, credential-stuffing, or persistence tests without explicit approval in the thread.
8. Tie each finding to evidence and a plausible abuse path. Do not report vague hypotheticals.
9. Order findings by severity and business impact.
10. Note clean areas explicitly audited, skipped checks, and residual risk.
11. Name policy, tests, monitoring, or documentation updates needed to keep guidance aligned with code.

High-Value Checks