skills.rest
arbiterForge
arbiterForgeOFFICIAL
Explore all skills by this author →
WebsiteGitHub

security-architecture

Map attack surfaces and identify unmitigated STRIDE threats before implementation.

139|7|Updated May 8, 2026
Search Tags:#threat-modeling#stride#claude-code#security-review#attack-surface#boundary-analysis
One-click install
npx skills add https://github.com/arbiterForge/codeArbiter --skill security-architecture-arbiterforge
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: security-architecture
Source: https://github.com/arbiterForge/codeArbiter/tree/main/plugins/ca/skills/security-architecture
Command: npx skills add https://github.com/arbiterForge/codeArbiter --skill security-architecture-arbiterforge

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents teams from building sensitive features without first understanding their attack surface, security boundaries, and unresolved risks.

Core Features & Use Cases

  • Attack-surface mapping: Lists entry points, outbound calls, data sinks, and trust transitions for the scoped feature.
  • STRIDE analysis: Checks spoofing, tampering, repudiation, disclosure, denial of service, and privilege escalation with mitigation status.
  • Targeted escalation: Can route specialized concerns to security-reviewer or auth-crypto-reviewer when needed.
  • Use case: Before shipping a new payment or authentication workflow, use this Skill to catch boundary-crossing gaps and decide whether the design can proceed, needs constraints, or must stop.

Quick Start

Use the security-architecture skill to review the threat-model scope for your sensitive feature and return the surface, STRIDE findings, and verdict in a concise report.

Frequently Asked Questions about security-architecture

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

FAQPage Schema
How do I model security threats before implementing a new sensitive feature?▼

To model security threats before implementation, you map the feature's attack surface, identify trust transitions, and run a STRIDE analysis to check spoofing, tampering, repudiation, disclosure, denial of service, and privilege escalation.

What is attack surface mapping for architectural boundaries?▼

Attack surface mapping for architectural boundaries involves listing entry points, outbound calls, data sinks, and trust transitions for a scoped feature to identify unmitigated security threats before the code is written.

When do I need a STRIDE analysis for my codebase?▼

You need a STRIDE analysis when building sensitive features like payment or authentication workflows, adding new entry points, or reviewing code that has not yet been written to catch boundary-crossing gaps.

Do I need a security-controls.md file to perform threat modeling?▼

Yes, threat modeling requires a security-controls.md file to serve as the boundary source, which is then used to perform the STRIDE pass and determine whether the design can proceed, needs constraints, or must stop.

Can I escalate specific security findings to specialized reviewers?▼

Yes, you can escalate specialized security concerns by dispatching targeted analysis to a security-reviewer or auth-crypto-reviewer when the initial threat-model review identifies issues requiring deeper inspection.

Related Skills

Explore More Software Engineering Skills→
koya-altkoya-alt

threat_modeling

Generate a structured threat_model.md with assets, trust boundaries, and STRIDE threats.

Community
Intermediate
troykellytroykelly
10

security-reviewer

Execute the security-reviewer subagent for code vulnerability detection.

Community
Basic
dakshrawat298-gifdakshrawat298-gif

security-entry-point-analyzer

Map application entry points and input pathways to model the attack surface.

Community
Advanced
alexmaruccialexmarucci

static-analysis

Automate SAST and SCA scans to identify security and dependency vulnerabilities.

Community
Advanced