Security Reviewer (jeffallan) vs What Leaked About You (useosint)
Security Reviewer (jeffallan) and What Leaked About You (useosint) are both Security skills, so an agent choosing between them is matching on descriptions that overlap. Here is where they actually diverge.
Security Reviewer
jeffallan
Performs end-to-end security examinations of code, infrastructure, dependencies and secrets and compiles a prioritized audit report that assigns severity to each finding and lists concrete remediation steps. Unlike tools that only add inline comments, check authentication patterns, or scan a branch diff, this one is aimed at producing a compliance-aware, prioritized audit document rather than a quick pre-merge or single-file review.
1 scenario in the bank answer to it
What Leaked About You
useosint
Checks an email, username, phone, or name against curated data-breach services — Have I Been Pwned, DeHashed, IntelX and the like — to enumerate which breaches an identity appears in and read what those records reveal, chiefly the list of services the person actually used. It is breach-exposure reconnaissance about a person, not a codebase tool: it does not scan your repository for hardcoded secrets, and it never uses a leaked password to access anything — reading the exposure is the whole job.
2 scenarios in the bank answer to it
What is the difference between Security Reviewer (jeffallan) and What Leaked About You (useosint)?
- Security Reviewer (jeffallan)
- Performs end-to-end security examinations of code, infrastructure, dependencies and secrets and compiles a prioritized audit report that assigns severity to each finding and lists concrete remediation steps. Unlike tools that only add inline comments, check authentication patterns, or scan a branch diff, this one is aimed at producing a compliance-aware, prioritized audit document rather than a quick pre-merge or single-file review.
- What Leaked About You (useosint)
- Checks an email, username, phone, or name against curated data-breach services — Have I Been Pwned, DeHashed, IntelX and the like — to enumerate which breaches an identity appears in and read what those records reveal, chiefly the list of services the person actually used. It is breach-exposure reconnaissance about a person, not a codebase tool: it does not scan your repository for hardcoded secrets, and it never uses a leaked password to access anything — reading the exposure is the whole job.
Should I use Security Reviewer or What Leaked About You?
The clearest answer is a situation each one is unambiguously right for. Both of these are drawn from the game's question bank.
Reach for Security Reviewer when
An auditor is coming and wants one document that grades the whole system — app code, servers, third-party libraries, leaked secrets — with a severity on every issue and a fix for each, ranked worst-first.
security-reviewer-jeffallan produces the end-to-end, severity-ranked audit document spanning code, infrastructure, dependencies and secrets. security-review-owasp and security-review-waybarrios only look at a diff or branch for exploits; security-review-affaan-m is build-time guidance, not an audit. The tell is a ranked document across the whole system.
Reach for What Leaked About You when
While cleaning out a dusty server closet, you spot a sticky note with your 2014 gaming alias. You dive into dump trawlers to see which tiny subscription box sites and forgotten hobby forums once held that string, purely to build a hit list, never to touch a password field.
This skill performs targeted reconnaissance on a single individual’s historical data exposure, querying compiled leak indexes to discover which external services originally stored a given identifier, without attempting to exploit or access anything. It wins here because your scenario explicitly describes trawling dumps to catalogue which small third-party businesses once held your old tag, which maps exactly to that exposure-readout mission, whereas the other options focus on writing code scanners, patching dependencies, or sanitizing server error output.
What they have in common
Both are filed under Security, the axis along which they collide. That shared ground is what makes an agent pick between them on description alone — and what makes it pick wrong.
Nearby comparisons
Reading the difference is not the same as spotting it at speed. That is the game.
Today's session