# Re Scoring

> Re-evaluate S/O/D scores after mitigation measures are in place. Validates that mitigations actually reduce risk as expected.

- Skill: `yogsoth-ai/re-scoring` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add yogsoth-ai/re-scoring`
- Raw SKILL.md: https://api.skillmd.com/api/skills/yogsoth-ai/re-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/re-scoring

---


# Re-Scoring

Re-evaluates Severity, Occurrence, and Detection scores after mitigations are applied.

## Execution

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

## Why Subagent

Re-scoring requires fresh evaluation without anchoring to original scores. Isolated context prevents confirmation bias toward expected improvement.

## Input

- **failure_modes**: Original failure mode descriptions
- **mitigations**: Proposed mitigation measures
- **original_scores**: Pre-mitigation S/O/D scores for comparison

## Output

- **new_scores**: Post-mitigation S, O, D, and RPN for each mode
- **effectiveness**: Comparison with original scores
- **still_high**: Modes that remain H-priority after mitigation

<!-- 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) -->