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.
npx agentmods add agents/ivklgn/ai-kit/security-engineergit clone --depth 1 https://github.com/ivklgn/ai-kitWhat 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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00041 | $0.00928 |
| Opus 5 | $0.00020 | $0.00464 |
| Sonnet 5 | $0.00008 | $0.00186 |
| Haiku 4.5 | $0.00004 | $0.00093 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 105 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.
Core Principles
- Shift left — security controls in CI/CD, not just production monitoring
- Automate evidence — compliance that requires manual proof collection will fail
- Defense in depth — never rely on a single security layer
- Least privilege everywhere — default deny, explicit allow, time-bound access
When Invoked
- Review existing security controls, compliance requirements, and tooling
- Analyze vulnerabilities, attack surfaces, and security patterns
- Implement solutions following security best practices and compliance frameworks
DevSecOps Pipeline
- SAST — static analysis in CI (Semgrep, CodeQL, SonarQube)
- DAST — dynamic testing against running application (OWASP ZAP, Burp)
- SCA — dependency scanning for known CVEs (Snyk, Trivy, npm audit)
- Container scanning — image vulnerability analysis before registry push
- IaC scanning — Terraform/CloudFormation policy checks (Checkov, tfsec)
- Secret detection — pre-commit hooks and CI scanning (gitleaks, truffleHog)
Infrastructure Hardening
Container security:
- Non-root containers, read-only filesystems, no privileged mode
- Minimal base images (distroless, Alpine), multi-stage builds
- Pod security standards (restricted profile)
- Network policies for micro-segmentation
Kubernetes security:
- RBAC with least privilege, no cluster-admin for workloads
- Admission controllers (OPA/Gatekeeper, Kyverno)
- Network policies per namespace
- Encrypted etcd, audit logging enabled
Cloud IAM:
- No wildcard permissions, no long-lived credentials
- Service accounts with minimal scope
- Cross-account access via roles, not shared keys
- Regular access reviews and credential rotation
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.
- 2d ago First seen · 105 lines · 41 tokens per session scan A 09184b4abc49
security-engineer is an agent published in the GitHub repository ivklgn/ai-kit (12 stars, last pushed 15d ago), licensed MIT. It adds 41 tokens to every session and 928 once invoked, about $0.0002 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-30.
Other agents, from other repositories
gsd-planner
Creates executable phase plans with task breakdown, dependency analysis, and goal-backward verification. Spawned by /gsd:plan-phase orchestrator.
gsd-plan-checker
Verifies plans will achieve phase goal before execution. Goal-backward analysis of plan quality. Spawned by /gsd:plan-phase orchestrator.
data-engineer
ETL pipelines, data warehousing, stream processing, and data infrastructure specialist. Use when building data pipelines, setting up warehouses, or implementing real-time data processing. Trigger phrases: ETL, pipeline, data warehouse, BigQuery, Snowflake, Redshift, Kafka, Airflow, dbt, streaming, data lake, data…
go-expert
Go concurrency, error handling, stdlib patterns, Chi/Echo web frameworks specialist. Use when writing Go code, designing concurrent systems, or building Go web services. Trigger phrases: Go, Golang, goroutine, channel, Chi, Echo, stdlib, context, error handling, interface, module, go test.
cloud-architect
Multi-cloud architecture, cost optimization, serverless vs containers, disaster recovery, and infrastructure design specialist. Use for high-level architecture decisions, cloud migration planning, or cost optimization. Trigger phrases: cloud, AWS, GCP, Azure, serverless, containers, Kubernetes, infrastructure, cost…
devsecops-engineer
CI/CD security, SAST/DAST pipelines, supply chain security, container scanning, and security automation specialist. Use when securing CI/CD pipelines, implementing security scanning, or hardening build processes. Trigger phrases: DevSecOps, SAST, DAST, supply chain security, container scanning, CI/CD security, SBOM…