Claude skills for Security

8 skills in the bank are filed under Security. They are grouped here because they compete for the same jobs — which is the reason an agent reaching for one of them sometimes gets another.

• Dependency UpdatersoftaworksWorks over a project's dependency manifest — detecting the language, applying the safe minor and patch bumps on its own, pausing on major versions, and running that ecosystem's vulnerability audit (npm audit, pip-audit, govulncheck, cargo audit and the like) to flag known-vulnerable packages. It secures the supply chain around your code, not the code itself: it does not scan your own source for bugs, write detection rules, or reason about a design's threats.
• Secure Error HandlingharperaaA secure-coding pattern for the error path: return generic, environment-aware messages to users while logging the detail server-side, so a stack trace, database error, or file path never hands an attacker a map of your system. It shapes how failures are surfaced — not a scanner that finds the leaks for you, and narrower than a full security review: it does not cover auth, input validation, or the other vulnerability classes, only how errors are reported.
• Security Reviewaffaan-m/eccHelps developers implement secure features by listing concrete checks and recommended patterns for authentication, input handling, secret management, API endpoints, and payment or sensitive flows. Unlike similarly named tools that scan code or produce vulnerability audits, this one focuses on design-time guidance and implementation checklists — it does not run automated SAST, assign severity scores, or perform penetration-style audits of diffs.
• Security ReviewSentryHunts only for exploitable security holes — injection, XSS, broken auth, weak crypto — and deliberately stays quiet unless it can point at attacker-controlled input reaching a vulnerable pattern. It reports high-confidence findings only, so a clean run is not proof of safety.
• Security Reviewwaybarrios/opencode-power-packInspects the unmerged commits on a branch and calls out concrete security problems that show realistic exploitation paths, so reviewers can decide whether changes are safe to merge. Unlike broader security-audit or SAST-style tools, it intentionally skips stylistic, architecture, dependency-wide, or general code-review concerns and concentrates only on high-confidence, actionable vulnerabilities in the pending diff.
• Security ReviewerjeffallanPerforms 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.
• Semgrep Rule CreatortrailofbitsAuthors a custom Semgrep static-analysis rule for one specific bug or vulnerability pattern — building the match (or a taint-mode source-to-sink data flow), then the paired vulnerable-and-safe test cases that keep false positives in check. Its output is a reusable detection rule, not a finished audit: it does not run existing Semgrep rulesets over your repo, triage the findings a scan produces, or review a diff by hand.
• What Leaked About YouuseosintChecks 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.