senior-security
STRIDE threat modeling, DREAD risk scoring, secret detection, and secure architecture design. Use when conducting threat models, reviewing code for vulnerabilities, designing defense-in-depth, or scanning for hardcoded secrets.
How do I install this agent skill?
npx skills add https://github.com/borghei/claude-skills --skill senior-securityIs this agent skill safe to install?
- Gen Agent Trust Hubpass
The skill provides a comprehensive set of security engineering tools, including STRIDE threat modeling and a regex-based secret scanner. No malicious behavior, data exfiltration, or dangerous obfuscation was detected. The scripts are well-documented and focus on legitimate application security tasks. Static analysis flags for dynamic imports are benign, as they are used only for timestamping reports.
- Socketwarn
1 alert: gptAnomaly
- Snykfail
Risk: CRITICAL · 1 issue
- Runlayerwarn
1/1 file flagged
- ZeroLeakspass
Score: 93/100 · 2 sections analyzed
What does this agent skill do?
Senior Security Engineer
The agent performs STRIDE threat analysis with DREAD risk scoring, designs defense-in-depth security architectures with Zero Trust principles, conducts secure code reviews against OWASP Top 10, and scans codebases for hardcoded secrets across 20+ credential patterns.
Core Capabilities
- Threat modeling — STRIDE per-element analysis, DREAD risk scoring, DFD creation, attack trees, and mitigation mapping.
- Security architecture — defense-in-depth layering, Zero Trust, authentication pattern selection (OAuth/OIDC, JWT, mTLS, FIDO2), and encryption strategy.
- Vulnerability assessment — automated (SAST/DAST/dependency/secret) plus manual testing, OWASP Top 10 mapping, severity classification, and remediation tracking.
- Secure code review — auth/authz, data handling, and crypto review with a checklist and secure-vs-insecure pattern catalog.
- Incident response — triage, containment, eradication, recovery, post-mortem, with severity tiers and runbook checklist.
- Secret detection —
secret_scanner.pyfinds 20+ credential patterns (AWS/GCP/Azure, GitHub/Slack/Stripe, private keys); CI/CD-ready exit codes. - Compliance mapping — OWASP ASVS, CIS Benchmarks, NIST CSF, PCI-DSS, HIPAA, SOC 2 at the application layer.
When to Use
- Conducting a threat model or attack-surface analysis on a system or component.
- Reviewing code for vulnerabilities before deployment.
- Designing a secure, defense-in-depth or Zero Trust architecture.
- Scanning a codebase for hardcoded secrets and credentials.
- Running a vulnerability assessment or planning incident response.
Routing: operational scanning, CVE triage and compliance evidence belong to senior-secops;
auditing a third-party skill before installing it belongs to skill-security-auditor. This
skill is for designing and reviewing your own system.
Clarify First
Before the threat model or scan, settle the inputs below. When one is missing or vague and would change the result, ask about it; when it wouldn't, use a sensible default and say which one you used.
- Target component/system: what to threat-model or scan; for a real model, its data flows (
--design), otherwise the component type (--component). - Assets & trust boundaries: what is being protected and where untrusted input enters (drives DREAD scoring and mitigations).
- Task: threat model / code vuln review / secret scan / incident-response plan (selects the tool and the output).
Ask about the two or three inputs that matter most for this request, not the whole list. If the user wants a result straight away, produce it and state your assumptions at the top.
Tools Overview
| Tool | Purpose | Example (runs as written) |
|---|---|---|
threat_modeler.py --design | Derive STRIDE threats per data flow from a JSON model: missing authentication, encryption, validation, rate limiting, logging or least privilege; sensitive data raises severity | python scripts/threat_modeler.py --design assets/sample_design_flawed.json |
threat_modeler.py --component | Generic STRIDE checklist for a component type (same output for any design: use it as a prompt list, not as the model) | python scripts/threat_modeler.py --component "API Gateway" --json |
secret_scanner.py | Hardcoded secrets across 20+ patterns (--severity, --format text/json, -o, --list-patterns) | python scripts/secret_scanner.py assets/sample_secrets_flawed.js |
Design file format: {"name": ..., "flows": [{"from", "to", "data", "crosses_boundary", "authenticated", "encrypted", "validated", "rate_limited", "logged", "least_privilege"}]}.
Flags you leave out are reported as "Unspecified controls" rather than guessed.
Exit codes: 0 nothing High/Critical (--design) or no critical/high secret; 1 the design
has High/Critical threats or a critical/high secret was found; 2 bad input (missing or
invalid file or path). Samples: sample_design_flawed.json exits 1 (an unauthenticated,
unencrypted internal payment hop), sample_design_sound.json exits 0;
sample_secrets_flawed.js (Amazon's documentation example key and a literal password)
exits 1, sample_secrets_clean.js exits 0.
References
Load the reference that matches the task — keep this file lean and pull detail on demand:
- references/security-workflows.md — the 5 full workflows (threat modeling, security architecture, vulnerability assessment, secure code review, incident response) with all decision matrices (STRIDE, OWASP Top 10, severity, code-review checklist), the security tools catalog, compliance frameworks, security headers, anti-patterns, troubleshooting table, and success criteria. Read when executing any security workflow.
- references/threat-modeling-guide.md — STRIDE methodology, attack trees, DREAD scoring, DFD creation, threat templates. Read when building a threat model.
- references/security-architecture-patterns.md — Zero Trust, defense-in-depth, authentication patterns (OAuth/PKCE, JWT, MFA), API security, data protection, secret management. Read when designing secure architecture.
- references/cryptography-implementation.md — AES-GCM, ChaCha20, RSA, Ed25519, password hashing (Argon2/bcrypt), HMAC, key management/rotation, HSM integration, common crypto mistakes. Read when implementing or reviewing cryptography.
- references/tool-reference.md — full flag tables, usage examples, and output formats for
threat_modeler.pyandsecret_scanner.py. Read when running the bundled scripts.
Scope & Limitations
This skill covers:
- Application-level security: threat modeling, secure code review, secret detection, and vulnerability assessment for web applications and APIs.
- Security architecture design: defense-in-depth layering, Zero Trust patterns, authentication/authorization model selection, and encryption strategy.
- Incident response planning: severity classification, containment procedures, post-mortem frameworks, and runbook creation.
- Compliance mapping: OWASP ASVS, CIS Benchmarks, NIST CSF, PCI-DSS, HIPAA, and SOC 2 alignment at the application layer.
This skill does NOT cover:
- Infrastructure and cloud security hardening (see senior-devops and aws-solution-architect).
- Runtime security monitoring, SIEM rule authoring, and SOC operations (see senior-secops).
- Full regulatory compliance programs, audit evidence collection, and certification processes (see ra-qm-team).
- Network penetration testing tooling, red team operations, and physical security assessments.
Integration Points
| Skill | Integration | Data Flow |
|---|---|---|
| senior-devops | CI/CD pipeline security gates | Threat model mitigations feed into pipeline hardening requirements; secret scanner runs as a pre-commit or CI step |
| senior-secops | Security monitoring and incident response | Threat model outputs define detection rules; incident severity levels align with SecOps alerting tiers |
| senior-backend | Secure API development | Secure code review checklist applied to backend PRs; authentication pattern selection guides API auth implementation |
| senior-architect | Security architecture decisions | Defense-in-depth layers and Zero Trust principles inform architecture design reviews; STRIDE results feed architecture risk register |
| senior-qa | Security testing integration | Vulnerability assessment findings become QA regression test cases; OWASP Top 10 mapping drives security test coverage |
| ra-qm-team | Compliance framework alignment | Security controls mapped to SOC 2, PCI-DSS, and HIPAA requirements; threat model documentation satisfies audit evidence needs |
Anti-Patterns
A Threat Model Without Data Flows
Mistake: Listing generic STRIDE threats for "the API" and calling it a threat model.
Why it happens: Checklists are quick and look complete.
Instead: Draw the flows and trust boundaries first, then ask what each flow lacks. --design makes that explicit; --component is only a prompt list.
Trusting the Internal Network
Mistake: Leaving service-to-service calls unauthenticated and unencrypted because they are "inside". Why it happens: The perimeter feels like a boundary. Instead: Treat every hop between services as a trust boundary (Zero Trust): mutual authentication and TLS internally too. The flawed sample shows the resulting Critical findings.
Rotating Nothing After a Secret Leak
Mistake: Deleting a committed key from the file and moving on. Why it happens: The scanner goes quiet once the line is gone. Instead: The key is in git history and possibly in clones and CI logs. Revoke and rotate it first, then remove it from history if policy requires.
Files
| File | Purpose |
|---|---|
scripts/threat_modeler.py | Design-driven STRIDE analysis and component checklists with DREAD scoring |
scripts/secret_scanner.py | Hardcoded secret detection |
assets/sample_design_flawed.json, sample_design_sound.json | Data-flow models (exit 1 / exit 0) |
assets/sample_secrets_flawed.js, sample_secrets_clean.js | Secret-scanner fixtures (exit 1 / exit 0) |
references/*.md | Workflows, threat-modeling guide, architecture patterns, cryptography, tool reference |
How can the creator link this skill?
Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.
<a href="https://skillzs.dev/skills/borghei/claude-skills/senior-security">View senior-security on skillZs</a>