# Remediation And Verification

> Turn AgentSec evidence into small, root-cause fixes with focused regression tests and a retest record. Use after an audit identifies a confirmed issue, security design gap, or high-confidence dependency risk.

- Skill: `0xcryptj/remediation-and-verification` (Agent Skill)
- Install (CLI): `npx skillmds@latest add 0xcryptj/remediation-and-verification`
- Raw SKILL.md: https://api.skillmd.com/api/skills/0xcryptj/remediation-and-verification/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Security
- License: MIT
- Author: 0xcryptj (https://skillmd.com/u/0xcryptj)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/0xcryptj/remediation-and-verification

---


# Remediation and Verification

## When to Use

Use this capability when an AgentSec finding has enough evidence to change code, configuration, dependencies, or deployment policy and the result must be demonstrated rather than assumed.

## Prerequisites

- A specific finding with evidence and affected location.
- Understanding of the application trust boundary and intended behavior.
- A focused test or deterministic check that can be rerun.

## Workflow

1. State the root cause, attacker-controlled input or authority boundary, and impact.
2. Implement the smallest idiomatic fix in the existing stack.
3. Add or update a focused regression test where practical.
4. Run the relevant scanner plus normal project tests.
5. Record what was verified and any provider/runtime control that remains review-needed.

## Verification

The fix is complete only when the regression test passes, the focused security check no longer produces the same evidence, and the report or change notes explain residual risk and operational follow-up.