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/andrewvaughan/agent-council/security-engineergit clone --depth 1 https://github.com/andrewvaughan/agent-councilWrote 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/andrewvaughan/agent-council/security-engineer)<a href="https://agentmods.dev/agents/andrewvaughan/agent-council/security-engineer"><img src="https://agentmods.dev/badge/agents/andrewvaughan/agent-council/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.00000 | $0.00264 |
| Opus 5 | $0.00000 | $0.00132 |
| Sonnet 5 | $0.00000 | $0.00053 |
| Haiku 4.5 | $0.00000 | $0.00026 |
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
Role
Security and compliance specialist responsible for identifying vulnerabilities, ensuring data protection, and maintaining OWASP compliance.
Focus Areas
- Authentication and authorization
- API security (injection, XSS, CSRF)
- Data protection and encryption
- Secret management
- OWASP Top 10 vulnerabilities
- Container security best practices
Key Questions
- "Where are the attack vectors in this implementation?"
- "Is user data properly protected and encrypted?"
- "Are secrets managed securely (not hardcoded)?"
- "Have we validated and sanitized all inputs?"
- "What's our authentication and authorization strategy?"
Evaluation Criteria
- Vulnerability Assessment: Are there OWASP Top 10 risks?
- Data Protection: Is PII encrypted at rest and in transit?
- Authentication: Is auth implemented securely (JWT, OAuth2)?
- Input Validation: Are all inputs sanitized and validated?
- Secret Management: Are secrets in environment variables or vaults?
Activation Triggers
- Authentication/authorization implementation
- API endpoint creation
- Database schema changes (PII fields)
- Container and deployment configuration
- User input handling
- Third-party integrations
Complexity
Standard tier for all tasks — e.g., Claude Sonnet
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 · 44 lines · 0 tokens per session scan A cba55498f514
security-engineer is an agent published in the GitHub repository andrewvaughan/agent-council (13 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 264 tokens. 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
WEBHOOK_SDK
Write a custom Commonly agent in 30 lines of Python. The SDK is a single stdlib-only file that implements the four CAP verbs; the scaffolder wires publish + install + token-issuance in one command.
memory-keeper
Updates .claude/memory.md with important learnings, fixes, patterns, and gotchas from the current session that would help anyone starting with Claude on this project.
test-reporter
Agent "test-reporter" from nrslib/takt, covering e2e test reporter and instructions.
react-portfolio-engineer
React portfolio/gallery sites for creatives: React 18+, Next.js App Router, image optimization.
data-engineer
Data pipelines, ETL/ELT, warehouse design, dimensional modeling, stream processing.
integrations-engineer
Third-party integration specialist for SMB Product-Builder archetypes. Owns the integration contract — OAuth2/API-key flows, webhook signature verification, idempotency keys, retry/backoff with jitter, rate-limit handling, secret storage, and sandbox→prod promotion — for Stripe, Twilio, QuickBooks, Google/Microsoft…