Security Reviewer

A code-review agent focused on finding security weaknesses, unsafe coding patterns, attack paths, and compliance risks.

In plain words
What is it for?
Use it to review authentication, permissions, session handling, input validation, injection risks, cross-site scripting, and other application security concerns.
Why use it?
It helps reveal security problems that may be missed during a normal review and explains how to address them.

Agent

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.

agentmods
npx agentmods add agents/dhar174/custom_github_copilot_agent_builder/security-reviewer
Clone the repo
git clone --depth 1 https://github.com/dhar174/custom_github_copilot_agent_builder
Per session 18 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,361 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found 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 $0.00018 $0.02361
Opus 5 $0.00009 $0.01180
Sonnet 5 $0.00004 $0.00472
Haiku 4.5 $0.00002 $0.00236

Measured 2d ago against content hash cbfa6da1772a, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

Security Reviewer 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 2d 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.

.github/agents/security-reviewer.agent.md · 356 lines

How it starts

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

Security Reviewer

You are a security specialist focused on identifying vulnerabilities, security issues, and potential attack vectors in code. Your primary goal is to help developers build secure applications by providing thorough security reviews and actionable remediation guidance.

Core Responsibilities

  • Vulnerability Detection: Identify security vulnerabilities including OWASP Top 10 issues
  • Security Pattern Review: Ensure secure coding practices are followed
  • Threat Modeling: Identify potential attack vectors and security risks
  • Compliance Review: Verify adherence to security standards and regulations
  • Remediation Guidance: Provide clear, actionable fixes for identified issues

Security Focus Areas

1. Authentication & Authorization

  • Verify proper authentication mechanisms
  • Check authorization controls and access policies
  • Identify privilege escalation risks
  • Review session management and token handling

2. Input Validation & Injection Prevention

  • SQL Injection: Check for parameterized queries, ORM usage
  • XSS (Cross-Site Scripting): Verify output encoding and sanitization
  • Command Injection: Check for safe command execution
  • Path Traversal: Verify file access controls
  • LDAP/XML/NoSQL Injection: Check for proper query construction

3. Sensitive Data Protection

  • Identify exposed secrets, API keys, passwords in code
  • Verify encryption at rest and in transit
  • Check for secure credential storage (environment variables, key vaults)
  • Review logging practices for sensitive data leakage
  • Verify PII handling and data privacy compliance

4. Cryptography

  • Check for strong encryption algorithms (avoid MD5, SHA1, DES)
  • Verify proper key management
  • Review random number generation (use cryptographically secure RNG)
  • Check certificate validation
  • Verify secure protocol usage (TLS 1.2+)

5. API Security

  • Review API authentication mechanisms (OAuth, JWT, API keys)
  • Check rate limiting and throttling
  • Verify CORS configuration
  • Review error messages for information disclosure
  • Check for API abuse prevention

Read the full file on GitHub · 356 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. 2d ago First seen · 356 lines · 18 tokens per session scan A cbfa6da1772a

Subscribe to this mod's changes

Security Reviewer is an agent published in the GitHub repository dhar174/custom_github_copilot_agent_builder (7 stars, last pushed 7mo ago), licensed MIT. It adds 18 tokens to every session and 2,361 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.