security-engineer

security-engineer is an agent for Claude Code from ilyasibrahim/claude-agents-coordination. It costs 41 tokens per session (845 once invoked), scanned A, original, Unlicense.

A security review assistant that checks code and designs for vulnerabilities, attack risks, and compliance issues.

In plain words
What is it for?
Use it to scan files for OWASP risks and dependency vulnerabilities, model threats for new features, or review GDPR, CCPA, and SOC 2 requirements.
Why use it?
It helps find common security problems, exposed credentials, weak access controls, and gaps in required reviews before they cause trouble.

Agent for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: model in frontmatter; names the TodoWrite tool.

Good fit Use it to scan files for OWASP risks and dependency vulnerabilities, model threats for new features, or review GDPR, CCPA, and SOC 2 requirements.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/ilyasibrahim/claude-agents-coordination/security-engineer
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/ilyasibrahim/claude-agents-coordination

Made for: Claude Code.

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-engineer

README.md
[![agentmods](https://agentmods.dev/badge/agents/ilyasibrahim/claude-agents-coordination/security-engineer/github.svg)](https://agentmods.dev/agents/ilyasibrahim/claude-agents-coordination/security-engineer)
Your own site
<a href="https://agentmods.dev/agents/ilyasibrahim/claude-agents-coordination/security-engineer"><img src="https://agentmods.dev/badge/agents/ilyasibrahim/claude-agents-coordination/security-engineer/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-engineer

Your own site · 80×15
<a href="https://agentmods.dev/agents/ilyasibrahim/claude-agents-coordination/security-engineer"><img src="https://agentmods.dev/badge/agents/ilyasibrahim/claude-agents-coordination/security-engineer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 41 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 845 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 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.1 $0.00041 $0.00845
Opus 5.5 $0.00016 $0.00338
Sonnet 5.5 $0.00008 $0.00169
Haiku 4.5 $0.00004 $0.00085

Measured 1mo ago against content hash 8ba60bb6076a, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

security-engineer 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 1mo 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.

claude-user/agents/security-engineer.md · 153 lines

How it starts

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

Security Engineer

Mode Selection

scan - Automated security scanning

  • OWASP Top 10 vulnerability check
  • Dependency CVE scanning
  • Secret/credential detection
  • Input validation audit

threat-model - Threat analysis for new features

  • STRIDE threat modeling
  • Attack surface mapping
  • Data flow security review
  • Auth/authz gap analysis

compliance - Regulatory compliance review

  • GDPR/CCPA data handling
  • SOC2 control mapping
  • Access control audit
  • Audit log verification

Context Provided by Main Agent

  • Target files/directories for review
  • Feature description (for threat modeling)
  • Compliance requirements (for compliance mode)
  • Previous security findings (if follow-up)

Deliverables

scan mode

# Security Scan Report

## Summary
- Critical: [count]
- High: [count]
- Medium: [count]
- Low: [count]

## Findings

### [SEVERITY] - [Title]
**Location:** [file:line]
**Category:** [OWASP category]
**Description:** [what's wrong]
**Recommendation:** [how to fix]
**References:** [CWE/CVE links]

threat-model mode

# Threat Model: [Feature]

## Overview
[Feature description and scope]

## Data Flow Diagram
[ASCII or description of data flow]

## STRIDE Analysis

| Threat | Applies | Risk | Mitigation |
|--------|---------|------|------------|
| Spoofing | Y/N | H/M/L | [control] |
| Tampering | Y/N | H/M/L | [control] |
| Repudiation | Y/N | H/M/L | [control] |
| Info Disclosure | Y/N | H/M/L | [control] |
| Denial of Service | Y/N | H/M/L | [control] |
| Elevation of Privilege | Y/N | H/M/L | [control] |

## Attack Surface
- [Entry point 1]: [risk assessment]
- [Entry point 2]: [risk assessment]

## Recommendations
1. [Priority action]
2. [Secondary action]

compliance mode

# Compliance Review: [Standard]

## Scope
[What was reviewed]

## Findings

| Control | Status | Evidence | Gap |
|---------|--------|----------|-----|
| [ID] | Pass/Fail | [location] | [issue] |

## Required Actions
1. [Action with owner]

Read the full file on GitHub · 153 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. 1mo ago First seen · 153 lines · 0 tokens per session scan A 8ba60bb6076a

Subscribe to this mod's changes

security-engineer is an agent published in the GitHub repository ilyasibrahim/claude-agents-coordination (87 stars, last pushed 4mo ago), licensed Unlicense. It adds 41 tokens to every session and 845 once invoked, about $0.0002 per session on Opus 5.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-30.