security-engineer

security-engineer is an agent for Claude Code from vedanta/the-system. It costs 37 tokens per session (10,029 once invoked), scanned A, original, LGPL-3.0.

A security-engineering agent that checks an application’s technology stack for vulnerabilities, architecture-related risks, and compliance concerns. It also creates security documentation and can stop deployments when it finds critical issues.

In plain words
What is it for?
Use it for stack-specific vulnerability scanning, architecture-informed compliance checks, security documentation, and deployment blocking for critical findings.
Why use it?
Security checks can miss risks specific to the tools and architecture a project uses. This brings those checks and their documentation into the development and deployment process.

Agent for Claude Code

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

Good fit Use it for stack-specific vulnerability scanning, architecture-informed compliance checks, security documentation, and deployment blocking for critical findings.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/vedanta/the-system/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/vedanta/the-system

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/vedanta/the-system/security-engineer/github.svg)](https://agentmods.dev/agents/vedanta/the-system/security-engineer)
Your own site
<a href="https://agentmods.dev/agents/vedanta/the-system/security-engineer"><img src="https://agentmods.dev/badge/agents/vedanta/the-system/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/vedanta/the-system/security-engineer"><img src="https://agentmods.dev/badge/agents/vedanta/the-system/security-engineer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 37 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 10,029 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 unknown 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.00037 $0.10029
Opus 5.5 $0.00015 $0.04012
Sonnet 5.5 $0.00007 $0.02006
Haiku 4.5 $0.00004 $0.01003

Measured 1mo ago against content hash ff62f7e7a515, 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/agents/security-engineer.md · 1,191 lines

The source is not reproduced here

Licensed LGPL-3.0

The repository is licensed LGPL-3.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.

Read it on GitHub

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 · 1,191 lines · 37 tokens per session scan A ff62f7e7a515

Subscribe to this mod's changes

security-engineer is an agent published in the GitHub repository vedanta/the-system (9 stars, last pushed 7mo ago), licensed LGPL-3.0. It adds 37 tokens to every session and 10,029 once invoked, about $0.0001 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-31.

Related

Other agents, from other repositories

base-template-generator

Use this agent when you need to create foundational templates, boilerplate code, or starter configurations for new projects, components, or features. This agent excels at generating clean, well-structured base templates that follow best practices and can be easily customized. Examples: Context: User needs to start a…

ruvnet/ruflo · 0 tokens

project-coordinator

Coordinates multi-agent workflows for this project.

ruvnet/ruflo · 11 tokens

python-specialist

Python development specialist.

ruvnet/ruflo · 7 tokens

sanitization-auditor

Use proactively before any commit and whenever new content is added. Scans tracked files for private-project leaks - upstream private project names, internal absolute paths, proprietary domain logic (financial / portfolio / trading / prediction / tax / advisory specifics), customer data, secrets, internal endpoints…

Enovatr-Labs/SpecRoute · 125 tokens

runtime-architect

Use when building or updating runtime layouts under runtimes/, the MCP single-source-of-truth, or cross-vendor sync utilities under tools/. Owns the six copy-pasteable layouts at runtimes/.claude/, runtimes/.codex/, runtimes/.gemini/, runtimes/.kiro/, runtimes/.cursor/, and runtimes/.devin/, plus runtimes/mcp/…

Enovatr-Labs/SpecRoute · 154 tokens

skill-author

Use when designing or extending skills under skills/. Owns the folder-per-skill convention with SKILL.md, the portable SpecRoute contract (name + description) and vendor-native frontmatter, the skill-template/ canonical layout, and skills/examples/ folders. Ensures skills are interactive parameterized workflows with a…

Enovatr-Labs/SpecRoute · 114 tokens