security-development

Generate threat models, SBOMs, and CI security gates for software changes.

1|Updated May 15, 2026
One-click install
npx skills add https://github.com/Blaze-sports-Intel/uber-engineer --skill security-development
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: security-development
Source: https://github.com/Blaze-sports-Intel/uber-engineer/tree/main/plugins/uber-engineer/skills/security-development
Command: npx skills add https://github.com/Blaze-sports-Intel/uber-engineer --skill security-development

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

It helps you design and implement security improvements that actually reduce real risk, using threat modeling, secure defaults, and verification evidence—not just checklists.

Core Features & Use Cases

  • Threat modeling and mitigations: Create STRIDE/OWASP-driven threat models and map attacker behavior to concrete controls.
  • Secure development and dependency hygiene: Reduce supply-chain exposure with SBOMs, SCA/SAST/DAST gates, and secret management practices.
  • Incident readiness: Produce incident-response playbooks and run tabletop exercises to ensure operational capability.

Quick Start

Use this skill to run an evidence-backed security threat model for the payments surface and produce the mitigations and verification steps needed for launch.

Frequently Asked Questions about security-development

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

FAQPage Schema
How do I create a threat model for new application features?

Threat modeling for new application features uses STRIDE and OWASP methodologies to map attacker behaviors to concrete security controls and verification steps.

What's the best way to manage supply-chain risk with SBOMs and dependency scanning?

Managing supply-chain risk involves generating SBOMs, running SCA and SAST gates in CI pipelines, and enforcing secure defaults to reduce dependency exposure across modified application surfaces.

How do I set up CI security gates for SAST and DAST scanning?

Setting up CI security gates requires configuring SAST, DAST, and dependency scanning pipelines that inspect repository state and enforce evidence-based completion criteria across application surfaces.

Do I need an incident response playbook for secure development?

Incident readiness plans are essential for secure development, producing incident-response playbooks and running tabletop exercises to ensure operational capability during security events.

Can I integrate secrets management practices directly into my development workflow?

Secrets management practices integrate into development workflows by inspecting repository state, grounding controls in official sources, and verifying completion with defined evidence-based criteria.

When do I need to run an evidence-backed security threat model before launch?

Run an evidence-backed security threat model before launch when shipping secure changes requires verified mitigations, dependency controls, and incident readiness plans grounded in actual repository state.