review-severity-ladder
Skill220 starsChanged 20 days agoMITView on GitHub
Use when you need severity to mean the same thing across reviewers, specialists, and models — place each finding on one shared critical/high/medium/low/note rung by consequence rather than fix effort, keep severity separate from confidence, and declare the deliverable's reporting floor.
In this repository179 other files it gives its agents.
- AGENTS.mdAGENTS.md
- chrono/CLAUDE.mdCLAUDE.md
- CLAUDE.mdCLAUDE.md
- accessible-media-authoringSkill
- agentic-safety-auditSkill
- agent-prompt-engineeringSkill
- audio-event-map-authoringSkill
- auto-scaffoldSkill
- chain-constructSkill
- chain-construct-smart-contractSkill
- claim-verificationSkill
- code-reachability-auditSkill
- code-review-loopSkill
- color-theorySkill
- conversation-designSkill
- copy-refinementSkill
- cosmos-sdk-audit-checklistSkill
- cross-chain-bridge-auditSkill
- cross-file-relationship-synthesisSkill
- data-flow-traceSkill
- dedup-prior-art-checkSkill
- defi-invariant-checkSkill
- dependency-cycle-auditSkill
- dependency-health-triageSkill
- detection-as-codeSkill
- diff-aware-semgrep-scanSkill
- differential-reviewSkill
- dimensional-analysis-checkSkill
- dual-level-retrievalSkill
- durable-nonce-exploitationSkill
- erc1271-revert-data-checkSkill
- error-based-sstiSkill
- evm-audit-flowSkill
- figma-implement-designSkill
- findings-filterSkill
- forensic-timeline-authoringSkill
- game-design-fundamentalsSkill
- game-mechanics-balancingSkill
- head-tailSkill
- incident-response-runbookSkill
- interactive-audio-designSkill
- interface-ambiguity-checkSkill
- keyword-clusteringSkill
- knowledge-base-integrationSkill
- known-advisory-backport-checkSkill
- layered-analysis-loopSkill
- level-design-patternsSkill
- locale-adaptationSkill
- multi-stance-audit-fanoutSkill
- narrative-structureSkill
- osint-platform-auditSkill
- parser-differential-route-confusionSkill
- persuasive-technical-writingSkill
- platform-complianceSkill
- player-engagement-psychologySkill
- pre-audit-threat-modelSkill
- program-rubric-lookupSkill
- read-only-reentrancy-checkSkill
- requirements-elicitationSkill
- rule6-rights-gateSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 12
Place each finding on the ladder by consequence, not by effort to fix and not by how interesting it is:
- Distinctive: line 23
When the ladder produces repeated critical findings on the same mechanism, the correct move is to remove or bound the mechanism, not to …
- Distinctive: line 26
Every finding carries exactly one rung and a one-line consequence statement.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Review Severity Ladder
Rank findings on one shared ladder so severity means the same thing across reviewers, specialists, and models.
Steps
- Place each finding on the ladder by consequence, not by effort to fix and not by how interesting it is:
- critical — data loss, credential exposure, unauthorized state change, or silent corruption reachable on a normal path.
- high — wrong results, broken invariant, or availability loss on a reachable path; correct behavior depends on luck.
- medium — wrong behavior on an edge, boundary, or error path; degraded but recoverable.
- low — quality, clarity, or duplication that will cause a future defect but causes none now.
- note — observation with no defect claim.
- Justify each placement with the consequence and the path that reaches it. "Could be a problem" is not a placement.
- Apply the reachability test before assigning critical or high: name the entry point, the actor, and the input that gets there. Unreachable code caps at medium.
- Apply the intrinsic-impact test: a finding that only reveals information already disclosed, or that requires privileges the attacker would not have, does not clear high.
- Separate severity from confidence. A high-severity finding you are unsure of is
high / unconfirmed— never demote severity to express doubt, and never inflate confidence to justify severity. - Set a severity floor for the deliverable and report everything at or above it; list the rest as notes rather than discarding them.
- When the ladder produces repeated critical findings on the same mechanism, the correct move is to remove or bound the mechanism, not to keep escalating the threat model.
Acceptance
- Every finding carries exactly one rung and a one-line consequence statement.
- Critical and high findings name entry point, actor, and reaching input.
- Severity and confidence are recorded as separate fields.
- The deliverable states its severity floor.
- Placements are defensible without reference to how hard the fix is.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

