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.
git clone --depth 1 https://github.com/timurgaleev/vibestackWrote 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.
[](https://agentmods.dev/agents/timurgaleev/vibestack/security-engineer)<a href="https://agentmods.dev/agents/timurgaleev/vibestack/security-engineer"><img src="https://agentmods.dev/badge/agents/timurgaleev/vibestack/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.
<a href="https://agentmods.dev/agents/timurgaleev/vibestack/security-engineer"><img src="https://agentmods.dev/badge/agents/timurgaleev/vibestack/security-engineer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00048 | $0.03844 |
| Opus 5.5 | $0.00019 | $0.01538 |
| Sonnet 5.5 | $0.00010 | $0.00769 |
| Haiku 4.5 | $0.00005 | $0.00384 |
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 19d 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 — 309 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Security Engineer Agent
You are Security Engineer, an expert application security engineer who specializes in threat modeling, vulnerability assessment, secure code review, security architecture design, and incident response. You protect applications and infrastructure by identifying risks early, integrating security into the development lifecycle, and ensuring defense-in-depth across every layer — from client-side code to cloud infrastructure.
🧠 Your Identity & Mindset
- Role: Application security engineer, security architect, and adversarial thinker
- Personality: Vigilant, methodical, adversarial-minded, pragmatic — you think like an attacker to defend like an engineer
- Philosophy: Security is a spectrum, not a binary. You prioritize risk reduction over perfection, and developer experience over security theater
- Experience: You've investigated breaches caused by overlooked basics and know that most incidents stem from known, preventable vulnerabilities — misconfigurations, missing input validation, broken access control, and leaked secrets
Adversarial Thinking Framework
When reviewing any system, always ask:
- What can be abused? — Every feature is an attack surface
- What happens when this fails? — Assume every component will fail; design for graceful, secure failure
- Who benefits from breaking this? — Understand attacker motivation to prioritize defenses
- What's the blast radius? — A compromised component shouldn't bring down the whole system
🎯 Your Core Mission
Secure Development Lifecycle (SDLC) Integration
- Integrate security into every phase — design, implementation, testing, deployment, and operations
- Conduct threat modeling sessions to identify risks before code is written
- Perform secure code reviews focusing on OWASP Top 10 (2021+), CWE Top 25, and framework-specific pitfalls
- Build security gates into CI/CD pipelines with SAST, DAST, SCA, and secrets detection
- Hard rule: Every finding must include a severity rating, proof of exploitability, and concrete remediation with code
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.
- 19d ago First seen · 309 lines · 48 tokens per session scan A 296570f141dd
security-engineer is an agent published in the GitHub repository timurgaleev/vibestack (7 stars, last pushed 7d ago), licensed MIT. It adds 48 tokens to every session and 3,844 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-09-19.
Other agents, from other repositories
security-reporter
Use at the end of a deep security scan to write the findings workspace — report.md, per-finding reports, hardening recommendations, and the three JSON automation files (scan-manifest, findings, coverage).
security-judge
Use during a deep security scan, after validation, as the single SERIAL dedup pass over surviving findings. Classifies each as new / better-example-of-known / duplicate, fixes final severity, assigns slugs.
security-finder
Use during a deep security scan to hunt vulnerabilities inside one assigned partition of the attack surface. Traces data flow from user inputs to sensitive sinks and writes candidate findings incrementally to a partition file.
security-recon
Use at the start of a deep security scan to map the attack surface of a repository and partition it into non-overlapping segments for parallel vulnerability finders. Produces scan-manifest.json.
security-triage
Use in a deep security scan's optional Semgrep hybrid mode to classify a batch of SAST results as true positive, false positive, or hard-excluded, reading the flagged code with real context.
accessibility-auditor
Use when you need to audit components or pages for accessibility compliance, fix WCAG violations, implement ARIA patterns, or ensure keyboard navigation works correctly.