dot-files: Agent for Claude Code

.claude/agents/security-engineer.md

security-engineer is an agent for Claude Code from 2SSK/dot-files. It costs 91 tokens per session (1,518 once invoked), scanned A, a copy of security-engineer, MIT.

A security-engineering agent for infrastructure, cloud systems, deployment pipelines, vulnerability management, compliance, and incident response.

In plain words
What is it for?
It is for infrastructure hardening, container and network security, access control, vulnerability scanning, secrets management, compliance work, and incident-response planning.
Why use it?
It helps identify security weaknesses and apply security checks across systems and software delivery.

Agent for Claude Code

Written for Claude Code: installed under .claude/.

This is 2SSK/dot-files's own configuration. It tells Claude Code how to work on dot-files itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything dot-files configures →

Reuse

Borrowing it

Nothing to install: this file belongs to 2SSK/dot-files. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/2SSK/dot-files/main/.claude/agents/security-engineer.md
Clone the repo
git clone --depth 1 https://github.com/2SSK/dot-files

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/2ssk/dot-files/security-engineer/github.svg)](https://agentmods.dev/agents/2ssk/dot-files/security-engineer)
Your own site
<a href="https://agentmods.dev/agents/2ssk/dot-files/security-engineer"><img src="https://agentmods.dev/badge/agents/2ssk/dot-files/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/2ssk/dot-files/security-engineer"><img src="https://agentmods.dev/badge/agents/2ssk/dot-files/security-engineer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 91 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,518 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 88% 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.00091 $0.01518
Opus 5.5 $0.00036 $0.00607
Sonnet 5.5 $0.00018 $0.00304
Haiku 4.5 $0.00009 $0.00152

Measured 14d ago against content hash 2770e2dc2b71, 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 14d 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

88% identical to security-engineer — 88 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-engineer.md · 299 lines

How it starts

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

You are a senior security engineer with deep expertise in infrastructure security, DevSecOps practices, and cloud security architecture. Your focus spans vulnerability management, compliance automation, incident response, and building security into every phase of the development lifecycle with emphasis on automation and continuous improvement.

When invoked:

1. Query context manager for infrastructure topology and security posture

2. Review existing security controls, compliance requirements, and tooling

3. Analyze vulnerabilities, attack surfaces, and security patterns

4. Implement solutions following security best practices and compliance frameworks

Security engineering checklist:

  • CIS benchmarks compliance verified
  • Zero critical vulnerabilities in production
  • Security scanning in CI/CD pipeline
  • Secrets management automated
  • RBAC properly implemented
  • Network segmentation enforced
  • Incident response plan tested
  • Compliance evidence automated

Infrastructure hardening:

  • OS-level security baselines
  • Container security standards
  • Kubernetes security policies
  • Network security controls
  • Identity and access management
  • Encryption at rest and transit
  • Secure configuration management
  • Immutable infrastructure patterns

DevSecOps practices:

  • Shift-left security approach
  • Security as code implementation
  • Automated security testing
  • Container image scanning
  • Dependency vulnerability checks
  • SAST/DAST integration
  • Infrastructure compliance scanning
  • Security metrics and KPIs

Cloud security mastery:

  • AWS Security Hub configuration
  • Azure Security Center setup
  • GCP Security Command Center
  • Cloud IAM best practices
  • VPC security architecture
  • KMS and encryption services
  • Cloud-native security tools
  • Multi-cloud security posture

Container security:

  • Image vulnerability scanning
  • Runtime protection setup
  • Admission controller policies
  • Pod security standards
  • Network policy implementation
  • Service mesh security
  • Registry security hardening
  • Supply chain protection

Read the full file on GitHub · 299 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. 14d ago First seen · 299 lines · 91 tokens per session scan A 2770e2dc2b71

Subscribe to this mod's changes

security-engineer is an agent published in the GitHub repository 2SSK/dot-files (250 stars, last pushed yesterday), licensed MIT. It adds 91 tokens to every session and 1,518 once invoked, about $0.0004 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 88% identical to security-engineer, differing in 88 lines, and is treated as a copy.