Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →hypnguyen1209/finding-discipline
Use when about to record, claim, rate the severity of, or report any security finding — before marking anything [CONFIRMED] or writing it into the report
Passed 21 of 22 test cases with the skill, and 18 of 22 without it.
and 2 more in the full report
3 fixed18 passed either way1 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 3 test cases the skill fixed. Same model, same prompt, with and without the skill.
An auditor found an exposed internal IP address in headers and assumes standard default network routing without direct observation. What confidence tier applies to this underlying routing claim?
| Checked | Without skill | With skill |
|---|---|---|
| Assigns Medium confidence rating | Missed | Passed |
The instructions your model reads when the skill loads.
The Iron Law: No [CONFIRMED] without proof. A finding is a claim about real, demonstrated
impact — not a status code, a reflected string, or a hunch. This is the offensive equivalent of
test-driven development: the proof is the test, and the finding does not exist until it passes.
Violating the letter of this rule is violating its spirit.
[CONFIRMED] — impact demonstrated AND grounded in an evidence artifact that exists on disk.[POSSIBLE] — reachable but the class proof bar is not yet met. Keep digging; do not report as real.[INFO] — true but no security impact at the claimed severity.A status code is not impact. See skills/references/finding-evidence-standards.md:
SSRF needs the internal response; IDOR needs another principal's data; RCE needs command output;
XSS needs script execution; open redirect needs an external destination.
Before any finding is recorded or reported:
python skills/vulnerability-analysis/scripts/validate_findings.py --findings f.json --evidence ./evidence
— it rejects ungrounded findings and per-class false positives.finding-validator agent (PASS / KILL / DOWNGRADE).[CONFIRMED] survivor goes in the report. Severity must match what was demonstrated (CVSS honest).See skills/references/finding-validation-runtime.md for the 7-question gate.
If a function calls another, read the callee — do not infer what it does from its name.
sanitize(), is_safe(), validate_input() are exactly where vulnerabilities hide; a name is a
claim by the author, not evidence. The same applies to a config key, a decorator, or a CVE title:
open the thing before you reason about it. An unread dependency in a data-flow claim is a hole.
test cases passed, vs 18 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.