# Attack Resilience Scoring

> Compute overall resilience score (0.0-1.0) based on attack results, coverage, and vulnerability severity distribution.

- Skill: `yogsoth-ai/attack-resilience-scoring` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add yogsoth-ai/attack-resilience-scoring`
- Raw SKILL.md: https://api.skillmd.com/api/skills/yogsoth-ai/attack-resilience-scoring/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: yogsoth-ai (https://skillmd.com/u/yogsoth-ai)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/yogsoth-ai/attack-resilience-scoring

---


# Attack Resilience Scoring

Computes a quantitative resilience score for the artifact based on red team results.

## Execution

Subagent — spawned via subagent-spawning/spawn-agent.

## Why Subagent

Scoring requires calibrated judgment independent of attack or defense bias. The scorer must weigh findings objectively against coverage.

## Input

- **aggregated_findings**: Deduplicated vulnerability report from finding-aggregation
- **coverage_data**: What percentage of threat surfaces were tested, at what depth

## Output

- **resilience_score**: 0.0-1.0 overall score
- **dimension_scores**: Per-dimension breakdown (logical, empirical, methodological, practical)
- **confidence_in_score**: How much to trust the score given coverage gaps
- **verdict**: Pass/conditional-pass/fail with justification

<!-- BEGIN available-tables (generated) -->

## Available SOPs

Optional, no fixed order; the final leaf is always a sop.

| SOP | When to use |
| --- | --- |
| spawn-agent | Spawn a customized CC subagent with full MCP tool access. Used by SOPs that declare execution: subagent. |

<!-- END available-tables (generated) -->