security-judge

security-judge is an agent for Claude Code from gonzalezpazmonica/pm-workspace. It costs 20 tokens per session (641 once invoked), scanned A, a copy of security-judge, MIT.

A code-review agent focused on common application security problems, including injection, broken access control, leaked credentials, and unsafe input handling.

In plain words
What is it for?
Use it to review code for OWASP-style flaws, personal-data exposure, dependency risks, and weak cryptography.
Why use it?
It helps find vulnerabilities that can expose data, allow unauthorized actions, or compromise an application.

Agent for Claude Code

Written for Claude Code: installed under .claude/. Also seen: model in frontmatter; mentions OpenCode.

Part of the pm-workspace plugin — 124 commands, 75 agents shipped together

Good fit Use it to review code for OWASP-style flaws, personal-data exposure, dependency risks, and weak cryptography.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/gonzalezpazmonica/pm-workspace/security-judge
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Clone the repo
git clone --depth 1 https://github.com/gonzalezpazmonica/pm-workspace

Made for: Claude Code.

Or install pm-workspace, the plugin that ships this one along with the rest of its 124 commands, 75 agents.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for security-judge

README.md
[![agentmods](https://agentmods.dev/badge/agents/gonzalezpazmonica/pm-workspace/security-judge/github.svg)](https://agentmods.dev/agents/gonzalezpazmonica/pm-workspace/security-judge)
Your own site
<a href="https://agentmods.dev/agents/gonzalezpazmonica/pm-workspace/security-judge"><img src="https://agentmods.dev/badge/agents/gonzalezpazmonica/pm-workspace/security-judge/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for security-judge

Your own site · 80×15
<a href="https://agentmods.dev/agents/gonzalezpazmonica/pm-workspace/security-judge"><img src="https://agentmods.dev/badge/agents/gonzalezpazmonica/pm-workspace/security-judge.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 20 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 641 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 100% copy Near-identical to another mod in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00020 $0.00641
Opus 5 $0.00010 $0.00320
Sonnet 5 $0.00004 $0.00128
Haiku 4.5 $0.00002 $0.00064

Measured 9d ago against content hash c17236ee60bc, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

security-judge scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 9d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

Origin

This is a copy

100% identical to security-judge — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.claude/agents/security-judge.md · 78 lines

How it starts

The opening of the file, as written. The whole thing — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Security Judge

You are one of 5 judges in the Code Review Court. Your focus: security.

What you check

  1. Injection: SQL injection, command injection, XSS, template injection, path traversal
  2. Authentication/Authorization: missing auth checks, broken access control, privilege escalation
  3. Credentials: hardcoded secrets, API keys, tokens, connection strings in code
  4. PII exposure: personal data in logs, error messages, or unprotected endpoints
  5. Input validation: missing sanitization, type coercion, buffer boundaries
  6. Dependency risk: known-vulnerable imports, unsafe deserialization
  7. Cryptography: weak algorithms, hardcoded IVs, missing HTTPS enforcement

What you DON'T check

  • Logic correctness → correctness-judge
  • Architecture → architecture-judge
  • Naming/complexity → cognitive-judge
  • Spec compliance → spec-judge

Output format (YAML)

judge: "security-judge"
reviewed_at: "{ISO timestamp}"
files_reviewed: ["{file1}", "{file2}"]
verdict: "pass|conditional|fail"
findings:
  - id: "SEC-001"
    file: "{path}"
    line: {N}
    severity: "critical|high|medium|low|info"
    category: "injection|auth|credentials|pii|validation|crypto|dependency"
    description: "{what's wrong}"
    suggestion: "{how to fix}"
    auto_fixable: true|false
    owasp_ref: "A03:2021"
summary:
  total_findings: {N}
  critical: {N}
  high: {N}
  medium: {N}
  low: {N}

Severity guide (security-specific)

  • critical: exploitable remotely without auth, data breach risk
  • high: exploitable with low complexity, significant impact
  • medium: requires specific conditions, moderate impact
  • low: defense-in-depth improvement, not directly exploitable
  • info: hardening suggestion

Veto power

Security findings of severity critical or high trigger automatic verdict "fail" regardless of other judges. A security veto cannot be overridden by scoring — it must be fixed.

Reporting Policy (SE-066)

Coverage-first review under Opus 4.7. Ver docs/rules/domain/review-agents-reporting-policy.md. Cada finding con {confidence, severity}; filter downstream rankea.

Read the full file on GitHub · 78 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 9d ago First seen · 78 lines · 20 tokens per session scan A c17236ee60bc

Subscribe to this mod's changes

security-judge is an agent published in the GitHub repository gonzalezpazmonica/pm-workspace (49 stars, last pushed 6d ago), licensed MIT. It adds 20 tokens to every session and 641 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to security-judge, differing in 0 lines, and is treated as a copy.

Related

Other agents, from other repositories

cpp-reviewer

Expert C++ code reviewer specializing in memory safety, modern C++ idioms, concurrency, and performance. Use for all C++ code changes. MUST BE USED for C++ projects.

affaan-m/ECC · 41 tokens

reviewer

Read-only reviewer for an SDD implementation — checks that the change satisfies the acceptance criteria it claims (stage 1) and meets quality/convention/edge-case bars (stage 2). Use after a task (or the whole feature) reaches GREEN, before it's considered done. It reads the diff and the upstream artifacts and reports…

genkovich/sdd · 81 tokens

atomic-auditor

Final gate for a finished implementation. Dispatched exactly once after the implement-review loop goes green, never per iteration. Never touches the repo; its one write is the audit report into the task scratchpad. Audits the delivered work as a whole: cumulative spec compliance, cross-iteration coherence…

damusix/atomic-claude · 169 tokens

bt6-pr-auditor

Reviews one pull request in a BT6 codebase for correctness, research integrity, security, verification quality, and merge readiness.

elder-plinius/T3MP3ST · 32 tokens

Reviewer

Mandatory fast reviewer: validates every agent delegation output before acceptance. Checks acceptance criteria, file partitions, regressions, type safety, security basics.

monkilabs/opencastle · 30 tokens

security-auditor

Use this agent when reviewing local code changes or pull requests to identify security vulnerabilities and risks. This agent should be invoked proactively after completing security-sensitive changes or before merging any PR.

NeoLabHQ/context-engineering-kit · 40 tokens