security-engineer

Defines and enforces defense-in-depth security across entire software stacks.

3|Updated Feb 7, 2026
One-click install
npx skills add https://github.com/Develonaut/bnto --skill security-engineer-develonaut
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: security-engineer
Source: https://github.com/Develonaut/bnto/tree/main/.claude/skills/security-engineer
Command: npx skills add https://github.com/Develonaut/bnto --skill security-engineer-develonaut

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Senior security engineer persona that owns all trust boundaries, attack surfaces, and defense-in-depth across the entire stack. You identify and secure cross-cutting risk areas, ensuring robust protections from browser to backend to infrastructure.

Core Features & Use Cases

  • Boundary ownership and accountability across auth routing, data flows, and deployment surfaces.
  • Threat modeling, risk assessment, and security governance for all surfaces (auth, Convex, Go API, Rust engine, web app, file transit, infra, dependencies, and open-source exposure).
  • Defense-in-depth guidance with secure coding, configuration, and deployment practices; incident response planning and auditability.
  • Use Case: When auditing a public repository, you map all trust boundaries, validate controls, and propose concrete mitigations that close gaps.

Quick Start

Describe your current project’s trust boundaries and critical surfaces to secure, then propose a concrete, prioritized mitigation plan.

Frequently Asked Questions about security-engineer

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

FAQPage Schema
How do I map trust boundaries and attack surfaces across a web app and backend?

Mapping trust boundaries involves identifying critical data flows and cross-cutting risk areas across auth routing, backend APIs, and infrastructure. A structured security review then validates input controls and proposes concrete mitigations for each surface.

What is defense-in-depth and how does it apply to full stack security?

Defense-in-depth is a security strategy that enforces layered protections across the entire software stack. Applying it to auth, data flows, and infrastructure ensures robust risk mitigation and secure deployment practices across all exposed surfaces.

How do I perform a threat modeling assessment for a multi-service architecture?

Threat modeling for multi-service architectures requires defining trust boundaries across services like Go APIs and Rust engines. The process assesses cross-cutting risks, validates input validation controls, and establishes auditable security governance.

Can I use this approach to audit open-source dependencies and file transit security?

Yes, auditing open-source dependencies and file transit security is supported by defining boundary ownership across all surfaces. The review validates secure configuration, identifies exposure risks, and proposes prioritized mitigations to close gaps.

What is the best way to secure auth routing and implement secure coding practices?

Securing auth routing requires defining strict trust boundaries and applying defense-in-depth guidance. A structured security review validates access controls, ensures secure coding practices are followed, and provides auditable governance for deployment.