findings-filter
Skill220 starsChanged 20 days agoMITView on GitHub
Use when you are sitting on a pile of candidate findings and must cut it down to what is real, reachable, and worth reporting — run each through reproduce-from-clean, reachability, attacker-gain, precondition, and deduplicate-by-root-cause gates, then record which gate every dropped candidate failed.
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
- 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
- review-severity-ladderSkill
- rule6-rights-gateSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
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 18
Check each survivor against the intended audience's bar — a program's scope, an operator's threat model, a reviewer's severity floor — and …
- Distinctive: line 22
Every retained finding was reproduced, with the reproduction recorded.
≈ “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
Findings Filter
Filter a candidate finding set down to what is real, reachable, and worth someone's attention — before it reaches a report.
Steps
- Reproduce first. A finding that has not been reproduced from a clean state is a hypothesis; label it so or drop it.
- Apply the reachability gate: name the entry point, the actor, the privilege level, and the concrete input that reaches the defect. No path, no finding.
- Apply the impact gate: state what an attacker gains that they did not already have. Findings whose only outcome is disclosure of already-public information, or self-inflicted harm by a privileged user, do not survive.
- Apply the precondition gate: list every assumption the finding needs. If the preconditions are individually unlikely and jointly required, say so and rank accordingly.
- Deduplicate by root cause, not by symptom. Ten call sites of one unsafe helper are one finding with ten instances.
- Separate defects from hardening suggestions. Hardening is legitimate output but must not be presented at defect severity.
- Check each survivor against the intended audience's bar — a program's scope, an operator's threat model, a reviewer's severity floor — and drop what is out of scope rather than padding.
- For every dropped finding, record the gate it failed. The dropped list is evidence of thoroughness and prevents the same candidate being re-raised next pass.
Acceptance
- Every retained finding was reproduced, with the reproduction recorded.
- Each retained finding names entry point, actor, privilege, and reaching input.
- Each states the attacker's concrete gain, not just the anomaly.
- Findings are deduplicated by root cause, with instances listed underneath.
- Hardening is separated from defects, and every drop records which gate it failed.
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.

