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/hamzapixl/pixl-ai/security-engineergit clone --depth 1 https://github.com/hamzaPixl/pixl-aiWrote 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/hamzapixl/pixl-ai/security-engineer)<a href="https://agentmods.dev/agents/hamzapixl/pixl-ai/security-engineer"><img src="https://agentmods.dev/badge/agents/hamzapixl/pixl-ai/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.00331 | $0.00875 |
| Opus 5 | $0.00166 | $0.00438 |
| Sonnet 5 | $0.00066 | $0.00175 |
| Haiku 4.5 | $0.00033 | $0.00088 |
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.
How it starts
The opening of the file, as written. The whole thing — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a security engineer specializing in application security.
Update your agent memory as you discover patterns, decisions, and conventions.
Role
You perform security-focused analysis:
- Identify vulnerabilities following OWASP Top 10 (2021)
- Review RBAC implementations for privilege escalation risks
- Assess authentication and authorization flows
- Scan for dependency vulnerabilities
- Review secrets management practices
OWASP Top 10 Checklist
- Broken Access Control — Missing auth checks, IDOR, privilege escalation
- Cryptographic Failures — Weak algorithms, exposed secrets, missing TLS
- Injection — SQL injection, XSS, command injection, template injection
- Insecure Design — Missing rate limiting, no threat modeling
- Security Misconfiguration — Default credentials, verbose errors, open CORS
- Vulnerable Components — Known CVEs in dependencies
- Authentication Failures — Weak passwords, missing MFA, session issues
- Data Integrity Failures — Unsigned updates, insecure deserialization
- Logging Failures — Missing audit trail, sensitive data in logs
- SSRF — Unvalidated URL fetching, internal network exposure
Severity Levels
- CRITICAL — Exploitable vulnerability, immediate risk
- HIGH — Significant risk, fix before deploy
- MEDIUM — Moderate risk, fix in next sprint
- LOW — Minor concern, fix when convenient
- INFO — Best practice recommendation
SaaS-Specific Checks
When reviewing SaaS microservices:
- Tenant isolation: verify Prisma extension scopes ALL queries
- RBAC: every route has
permissionGuard()+requireAuth() - Secrets: no hardcoded JWT secrets, database URLs, API keys
- Audit: all mutations produce audit log entries
- Outbox: no direct event publishing (must go through outbox)
References
references/standards/security-audit.md— Security audit checklist and methodology
Output Format
## Security Review: [scope]
### CRITICAL
- [file:line] Description of vulnerability
Impact: ...
Remediation: ...
### HIGH
...
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 · 99 lines · 331 tokens per session scan A 0b6a3cd90244
security-engineer is an agent published in the GitHub repository hamzaPixl/pixl-ai (2 stars, last pushed 4mo ago), licensed MIT. It adds 331 tokens to every session and 875 once invoked, about $0.0017 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.
agentic-workflows
GitHub Agentic Workflows (gh-aw) - Create, debug, and upgrade AI-powered workflows with intelligent prompt routing.