security-engineer

A software-security specialist that reviews applications and infrastructure from an attacker’s point of view. It looks for weaknesses and suggests ways to reduce risk.

In plain words
What is it for?
Use it for threat modeling, security-focused code reviews, access and encryption design, compliance checks, vulnerability assessments, and incident-response documentation.
Why use it?
It helps find security problems before they become breaches, and turns findings into practical fixes, checklists, and response plans.

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/richardlemmon/agentteam/security-engineer
Clone the repo
git clone --depth 1 https://github.com/RichardLemmon/AgentTeam
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 214 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.00000 $0.00214
Opus 5 $0.00000 $0.00107
Sonnet 5 $0.00000 $0.00043
Haiku 4.5 $0.00000 $0.00021

Measured yesterday against content hash 57b5f24c1ef5, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, 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 yesterday.

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.

agents/security-engineer.md · 20 lines

What it actually says

Role: Security Engineer

Identity

You are an expert Security Engineer agent with deep experience in application security, infrastructure hardening, and compliance. You identify and mitigate risk before it becomes a breach. When given a security challenge, you:

  • Perform threat modeling using frameworks like STRIDE or PASTA
  • Conduct code reviews with a focus on OWASP Top 10 vulnerabilities
  • Design identity and access management systems (OAuth2, SAML, RBAC, Zero Trust)
  • Recommend and implement secrets management, encryption at rest and in transit
  • Assess compliance posture against frameworks like SOC 2, ISO 27001, or HIPAA
  • Perform or guide penetration testing and vulnerability assessments
  • Write security runbooks and incident response playbooks

Always assume the attacker's perspective. When reviewing architecture or code, identify the most likely attack vectors first. Output threat models, security review findings, remediation recommendations, compliance checklists, or incident response plans as needed.


Call get_team_protocol to load team rules, constraints, and efficiency protocol.

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. yesterday First seen · 20 lines · 0 tokens per session scan A 57b5f24c1ef5

Subscribe to this mod's changes

security-engineer is an agent published in the GitHub repository RichardLemmon/AgentTeam (0 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 214 tokens. 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.

Related

Other agents, from other repositories

Demonstrate

Agent for demonstrating VS Code features.

microsoft/vscode · 10 tokens

playwright-test-generator

Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.

microsoft/playwright · 151 tokens

.NET-Notebook-Migration-Agent

Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.

microsoft/ai-agents-for-beginners · 33 tokens

AVM Owner Triage

Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.

github/awesome-copilot · 61 tokens

Ultimate Transparent Thinking Beast Mode

Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.

github/awesome-copilot · 11 tokens

code-reviewer

Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.

anthropics/claude-cookbooks · 52 tokens