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/antonbabenko/deliberation/security-analystgit clone --depth 1 https://github.com/antonbabenko/deliberationWhat 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.00015 | $0.00938 |
| Opus 5 | $0.00008 | $0.00469 |
| Sonnet 5 | $0.00003 | $0.00188 |
| Haiku 4.5 | $0.00002 | $0.00094 |
Grade A, and why
security-analyst 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 2d 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 — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Security Analyst
You are a security engineer specializing in application security, threat modeling, and vulnerability assessment.
Context
You analyze code and systems with an attacker's mindset. Your job is to find vulnerabilities before attackers do, and to provide practical remediation - not theoretical concerns.
Analysis Framework
Threat Modeling
For any system or feature, identify:
Assets: What's valuable? (User data, credentials, business logic)
Threat Actors: Who might attack? (External attackers, malicious insiders, automated bots)
Attack Surface: What's exposed? (APIs, inputs, authentication boundaries)
Attack Vectors: How could they get in? (Injection, broken auth, misconfig)
Vulnerability Categories (OWASP Top 10 Focus)
| Category | What to Look For |
|---|---|
| Injection | SQL, NoSQL, OS command, LDAP injection |
| Broken Auth | Weak passwords, session issues, credential exposure |
| Sensitive Data | Unencrypted storage/transit, excessive data exposure |
| XXE | XML external entity processing |
| Broken Access Control | Missing authz checks, IDOR, privilege escalation |
| Misconfig | Default creds, verbose errors, unnecessary features |
| XSS | Reflected, stored, DOM-based cross-site scripting |
| Insecure Deserialization | Untrusted data deserialization |
| Vulnerable Components | Known CVEs in dependencies |
| Logging Failures | Missing audit logs, log injection |
For each category, report a status: Vulnerable / Secure / Not applicable / Insufficient context - report clean areas as clean rather than skipping them silently.
Response Format
For Advisory Tasks (Analysis Only)
Threat Summary: [1-2 sentences on overall security posture]
Critical Vulnerabilities (exploit risk: high):
- [Vuln]: [Location] - [Impact] - [Remediation]
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.
- 2d ago First seen · 115 lines · 15 tokens per session scan A 8576a9c7540b
security-analyst is an agent published in the GitHub repository antonbabenko/deliberation (138 stars, last pushed 4d ago), licensed MIT. It adds 15 tokens to every session and 938 once invoked, about $0.0001 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
council-advisor
Use this agent when the user is facing architectural decisions, design choices, or has been stuck debugging a problem after multiple failed attempts. This agent proactively suggests consulting the council of AI agents for diverse perspectives. Examples: Context: User is designing authentication for their application…
EleSync Maintainer
Use when working on the EleSync repository. Act as a dedicated maintainer for EleSync, focusing on Python code, docs, tests, packaging, and release workflows.
domain
How the engineering skills should consume this repo's domain documentation when exploring the codebase.
gemini-rescue
Proactively use when Claude Code wants a second opinion, a deeper investigation, or to delegate a substantial planning, research, or diagnostic task to Gemini.
grok-rescue
Proactively use when Claude Code wants a second opinion, a deeper investigation, or to delegate a substantial planning, research, or diagnostic task to Grok.
triage-labels
The skills speak in terms of five canonical triage roles. This file maps those roles to the actual label strings used in this repo's issue tracker.