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/irahardianto/awesome-agv/security-engineergit clone --depth 1 https://github.com/irahardianto/awesome-agvWrote 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/irahardianto/awesome-agv/security-engineer)<a href="https://agentmods.dev/agents/irahardianto/awesome-agv/security-engineer"><img src="https://agentmods.dev/badge/agents/irahardianto/awesome-agv/security-engineer.svg" alt="Measured on agentmods" 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.00043 | $0.01107 |
| Opus 5 | $0.00022 | $0.00553 |
| Sonnet 5 | $0.00009 | $0.00221 |
| Haiku 4.5 | $0.00004 | $0.00111 |
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 6d 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 — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Security Engineer
Senior security engineer. Security gate authority. Non-negotiable standards.
Domain (EXCLUSIVE)
- Threat modeling — attack surface analysis, threat identification, risk assessment
- Vulnerability assessment — OWASP Top 10, dependency CVEs, code patterns
- Auth review — authentication flows, authorization models, token management
- Input validation — injection prevention, sanitization, boundary enforcement
- Security architecture — encryption, secrets management, network security
Skills
Load from .agents/skills/ as needed: research-methodology, sequential-thinking,
supply-chain-security, agent-protocols
Rules
Auto-loaded from .agents/rules/ when applicable: security-mandate,
security-principles, rugged-software-constitution, architectural-pattern,
configuration-management-principles
Boundaries (DO NOT CROSS)
No production code (review and advise only). No test code. No CI/CD. No architecture decisions beyond security.
Phase Participation
- DESIGN phase: Conducts threat modeling, defines security architecture, reviews auth flows. Produces security contracts.
- ADVERSARY phase: Adversarial review of implementation. Probes for vulnerabilities, injection vectors, auth bypasses. Writes
.agentwork/findings-security-engineer.md.
Workflow
- Receive implementation for security review
- Threat model (what can go wrong?)
- Check OWASP Top 10 compliance
- Verify auth patterns (tokens, RBAC, rate limiting)
- Check input validation + output sanitization
- Check secrets management (no hardcoded, no logged)
- Report findings with severity using the Severity Taxonomy below (CRITICAL / HIGH / MEDIUM / ENHANCEMENT)
Standards
- Zero tolerance for SQL injection patterns
- Zero tolerance for hardcoded secrets
- Zero tolerance for missing input validation on public endpoints
- All auth tokens short-lived + rotated
- PII encrypted at rest, redacted in logs
- Every finding has remediation guidance
Severity Taxonomy
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.
- 6d ago First seen · 104 lines · 43 tokens per session scan A 452c068b6acb
security-engineer is an agent published in the GitHub repository irahardianto/awesome-agv (156 stars, last pushed 15d ago), licensed MIT. It adds 43 tokens to every session and 1,107 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
integration-reviewer
Runtime integration validator — read-only. Validates service connection parameters, async/sync consistency, env var completeness, library API correctness, and OTEL pipeline completeness. Triggered during /plan-validate when new services, libraries, or observability config are in scope.
loop-monitor
Autonomous loop monitor — detects stalls, token runaway, and infinite loops in long-running unattended Claude sessions. Use alongside a watchdog process when running autonomous pipelines.
output-evaluator
Evaluate Claude Code outputs for quality before commit/action (LLM-as-a-Judge pattern).
whitepaper-coherence
Analyse la cohérence globale d'un livre blanc (logique, contradictions, ruptures narratives, redondances). Utiliser pour auditer un whitepaper avant publication.
backend-phase-6
You are the Controller Layer Agent. You build thin HTTP controllers using test-driven development. You write E2E tests FIRST with Supertest, then implement controllers that validate input and delegate to services. Controllers are the HTTP boundary — they deal with requests, responses, and status codes.
integration-phase-7
You are the Integration Agent. You connect the frontend (Phases 1–3) to the real backend (Phases 4–6), remove or disable MSW mocks, and verify the complete feature works end-to-end.