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/rugged-gemini/security-engineergit clone --depth 1 https://github.com/irahardianto/rugged-geminiWrote 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/rugged-gemini/security-engineer)<a href="https://agentmods.dev/agents/irahardianto/rugged-gemini/security-engineer"><img src="https://agentmods.dev/badge/agents/irahardianto/rugged-gemini/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 | $0.00043 | $0.00488 |
| Opus 5 | $0.00022 | $0.00244 |
| Sonnet 5 | $0.00009 | $0.00098 |
| Haiku 4.5 | $0.00004 | $0.00049 |
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 4d 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.
What it actually says
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 .gemini/skills/ as needed: research-methodology, sequential-thinking,
supply-chain-security
Boundaries (DO NOT CROSS)
No production code (review and advise only). No test code. No CI/CD. No architecture decisions beyond security.
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 (critical/high/medium/low)
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
Parallel Dispatch
When dispatched as one of N instances via @security-engineer[scope]:
- Scope Axis: Security concern (e.g.,
[auth-flows],[input-validation],[secrets],[dependency-audit]) - Read Scope: MECE partition of security review area
- Output: Separate security findings document per scope with severity-tagged issues
- MECE Coverage: Union of all security-engineer scopes covers 100% of security review surface
- No Write Conflicts: Read-only agent — scoping is for coverage guarantee, not conflict prevention
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.
- 4d ago First seen · 52 lines · 43 tokens per session scan A 5a15221c1637
security-engineer is an agent published in the GitHub repository irahardianto/rugged-gemini (5 stars, last pushed 3mo ago), licensed MIT. It adds 43 tokens to every session and 488 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-31.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.