security-audit
Use when the user wants to audit code, dependencies, or infrastructure for security issues. Covers SAST, dependency scanning, secret leak detection, and OWASP-style checks.
- License 许可
- MIT
- 最近更新
- 2026-11-15
- Stars
- ★ 0
- Forks
- 1
01 前言 Front Matter
- name
- security-audit
- triggers
- [ "user", "model" ]
- description
- Use when the user wants to audit code, dependencies, or infrastructure for security issues. Covers SAST, dependency scanning, secret leak detection, and OWASP-style checks.
03 SKILL.md 正文
Security Audit
Defensive security analysis of code, dependencies, and configuration.
When to use
- User asks for a security review or audit.
- Adding untrusted dependencies or new secrets handling.
- Before exposing a service to the internet.
- After a security incident or alert.
Core protocol
- Scope the surface. Identify code paths, inputs, auth, secrets, and network boundaries.
- Run static analysis. Use project linters and SAST tools if available.
- Check dependencies. Run
python scripts/dep-audit.py(auto-detects ecosystems; shells to installed pip-audit/npm audit/cargo audit/osv-scanner). Missing scanners are reported as skipped, never installed.dep-audit-gate.py(PostToolUse on^exec$) already surfaces[DEP-AUDIT]findings after install commands. - Hunt for secrets. Run secret-scanning tools or grep for high-risk patterns.
- Review auth and input. Verify auth checks, input validation, output encoding, and least privilege.
- Document findings. Rank by severity; do not exploit, only detect.
Checklist - 5 security principles
Apply this checklist to every audit. Each item comes from the sec-needs source.
| Principle | What to verify | What to flag |
|---|---|---|
| 1. Minimize attack surface | Every line of code, every input, every endpoint, every service, every log line is a possible vector. | Unnecessary code, unauthenticated endpoints, public S3/storage URLs, sequential IDs on resource reads, sensitive data in logs, timing leaks in comparisons. |
| 2. Least privilege | Services, users, and DB access have only the permissions they need. | Over-privileged service accounts, broad IAM policies, DB access from outside the VPC, frontend code calling the DB directly, hardcoded credentials. |
| 3. Secure defaults | The default state is safe: hidden passwords with opt-in reveal, confirmation for destructive actions, MFA required, new accounts must change default password. | Default-visible passwords, destructive actions without confirmation, missing MFA prompts, insecure default credentials. |
| 4. Standard crypto | Sensitive data is encrypted with standard algorithms; no home-grown crypto. | Plain-text passwords, custom hash functions, missing bcrypt/argon2, unencrypted sensitive payloads. |
| 5. Updates and monitoring | Dependencies are patched promptly; SAST and WAF are in place. | Outdated dependencies with CVEs, missing Dependabot/renovate, missing SAST/WAF coverage. |
See also
code-review- general code review before merge.secure-defaults-check- pre-commit checklist for secure defaults.scan_secrets.py- existing script atskills/obsidian-workflow/scripts/scan_secrets.pyfor scanning Markdown files for secrets.
Output rule
- Produce a findings list: severity, file, issue, recommendation, and verification command.
- Never expose real credentials or attack a live system.
04 同仓库更多 Skills
montador-de-ideias
Use when assembling, expanding, or elevating a raw project idea or initial prompt into an ultra-detailed, first-principles dossier and compiled master prompt with journalistic OSINT market research, Tech Lead and Staff Architect justifications, atomic and modular hardening/optimization, and high-impact contact surfaces.
git-github-adaptive-engineering
Use when any task touches git history, GitHub issues/PRs/releases/CI, repo governance, or branch and merge decisions. Runs the Fase Zero situational-awareness battery, picks one of five delivery flows via the adaptive decision engine, and enforces commit/PR information-density standards. Orchestrates the gh, git-workflows, github-actions, pr, and debug/finish skills.
adaptive-agenda-calendar-routine-engine
Use when planning or executing work across hours, days, weeks, or sprints. Turns the calendar into a strict time-blocked agenda (HH:MM-HH:MM blocks carrying a routine profile, expected inputs, and a handoff output artifact), runs the 5-stage cognitive flow (Radar and Hunt -> Triage plus Steve Jobs conception -> workbench manifest -> >=32-cycle loop -> Close plus Open-Minded Scrum), and unfolds macro calendar milestones into micro agenda blocks through extensions/gcal/wrapper.py.
demo
Use when demonstrating a skill in a fixture project.
duplicate-skill
Use when testing duplicate skill name detection.
duplicate-skill
Use when testing duplicate skill name detection.