skills-catalog/ln-760-security-setup/SKILL.md
Sets up security scanning for secrets and dependency vulnerabilities. Use when adding security infrastructure to a project.
npx skillsauth add levnikolaevich/claude-code-skills ln-760-security-setupInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Paths: File paths (
shared/,references/,../ln-*) are relative to skills repo root. If not found at CWD, locate this SKILL.md directory and go up one level for repo root. Ifshared/is missing, fetch files via WebFetch fromhttps://raw.githubusercontent.com/levnikolaevich/claude-code-skills/master/skills/{path}.
Type: L2 Domain Coordinator Category: 7XX Bootstrap
Step 1: Detect Project Type
.gitleaks.toml, SECURITY.md)Step 2: Check Tool Availability
Step 3: Load Existing Configs
.gitleaks.toml exists: note for preservationSECURITY.md exists: note for update (not overwrite).pre-commit-config.yaml exists: check for gitleaks hookStep 1: Invoke ln-761 Secret Scanner
Step 2: Invoke ln-625 Dependencies Auditor (mode=vulnerabilities_only)
mode=vulnerabilities_onlyStep 1: Combine Findings
Step 2: Risk Assessment
Step 3: Build Summary
Step 1: Create/Update SECURITY.md
references/security_md_template.mdStep 2: Configure Pre-commit Hooks
.pre-commit-config.yaml missing: create from templatereferences/precommit_config_template.yamlStep 3: Generate CI Workflow
.github/workflows/security.yml missing: create from templatereferences/ci_workflow_template.yamlStep 4: Update .gitignore
.env, .env.*, !.env.example*.pem, *.keyCRITICAL: All delegations use Agent tool with
subagent_type: "general-purpose"for context isolation.
| Worker | Parallel | Purpose | |--------|----------|---------| | ln-761-secret-scanner | Yes | Hardcoded secret detection | | ln-625-dependencies-auditor | Yes | Vulnerability scanning (mode=vulnerabilities_only) |
Prompt template:
Agent(description: "Secret scanning via ln-761",
prompt: "Execute security scanner.
Step 1: Invoke worker:
Skill(skill: \"ln-761-secret-scanner\")
CONTEXT:
Project: {projectPath}",
subagent_type: "general-purpose")
Agent(description: "Dependency vulnerability scan via ln-625",
prompt: "Execute vulnerability scanner.
Step 1: Invoke worker:
Skill(skill: \"ln-625-dependencies-auditor\")
CONTEXT:
Project: {projectPath}
Mode: vulnerabilities_only (only CVE scan, skip outdated/unused checks)",
subagent_type: "general-purpose")
Pattern: Both workers can execute in parallel via Agent tool, then aggregate results.
Anti-Patterns:
- Phase 1: Invoke secret scanner ln-761 (pending)
- Phase 2: Invoke dependency auditor ln-625 (pending)
- Phase 3: Aggregate findings (pending)
- Phase 4: Generate security artifacts (pending)
- Phase 5: Return summary (pending)
MANDATORY READ: Load shared/references/meta_analysis_protocol.md
Skill type: planning-coordinator. Run after all phases complete. Output to chat using the protocol format.
| File | Purpose |
|------|---------|
| references/security_md_template.md | Template for SECURITY.md generation |
| references/precommit_config_template.yaml | Pre-commit hooks configuration |
| references/ci_workflow_template.yaml | GitHub Actions security workflow |
mode=vulnerabilities_only to ln-625 — full audit mode is not appropriate for bootstrap context.gitleaks.toml, SECURITY.md, or .pre-commit-config.yaml exist, update rather than overwritesubagent_type: "general-purpose" for all worker delegations (context isolation)Version: 3.0.0 Last Updated: 2026-02-05
testing
Drafts and publishes fact-checked GitHub Discussions announcements. Use for releases, updates, or project news; not for release creation or issue responses.
testing
Prepares and publishes a tagged GitHub release from repository evidence. Use for an explicit release request; not for ordinary commits, packages, or community news.
testing
Validates, commits, pushes, and remotely verifies approved repository changes. Use when publication is requested; not for releases, package publishing, or announcements.
development
Reviews standalone skills and their configured distribution surfaces before publication. Use for skill release readiness; not for product code or implementation-plan review.