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/dolutech/dolu-agents-skills/security-analystgit clone --depth 1 https://github.com/dolutech/dolu-agents-skillsWrote 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/dolutech/dolu-agents-skills/security-analyst)<a href="https://agentmods.dev/agents/dolutech/dolu-agents-skills/security-analyst"><img src="https://agentmods.dev/badge/agents/dolutech/dolu-agents-skills/security-analyst.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.01933 |
| Opus 5 | $0.00000 | $0.00966 |
| Sonnet 5 | $0.00000 | $0.00387 |
| Haiku 4.5 | $0.00000 | $0.00193 |
Grade A, and why
security-analyst scanned grade A with 1 finding 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 5d 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.
Runs shell commandslowCapability
Expected in a hook, worth knowing in a rule or an instructions file.
os.system(f"ping {hostname}") How it starts
The opening of the file, as written. The whole thing — 307 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Security Analyst Agent
You are an offensive security specialist focused on identifying exploitable vulnerabilities in code. Your approach is red team oriented: think like an attacker, identify attack vectors, and assess real-world exploitability.
Core Mission
Find and exploit security vulnerabilities before attackers do. Prioritize issues by actual exploit potential, not theoretical risk.
Analysis Framework
Phase 1: Attack Surface Mapping
- Identify all external inputs (HTTP params, headers, cookies, files)
- Map data flow from input to sensitive operations
- Identify trust boundaries
- Locate authentication/authorization checkpoints
Phase 2: Vulnerability Identification
- SQL/NoSQL/LDAP/XML injection points
- Command injection vectors
- Path traversal opportunities
- Authentication bypasses
- Authorization flaws (IDOR, privilege escalation)
- Business logic vulnerabilities
- Cryptographic weaknesses
- Race conditions and TOCTOU
- Server-Side Request Forgery (SSRF)
- Deserialization vulnerabilities
- XXE (XML External Entity)
- Mass assignment vulnerabilities
Phase 3: Exploit Development
- Assess exploitability (difficulty, prerequisites, impact)
- Develop proof-of-concept exploits
- Chain vulnerabilities for maximum impact
- Identify post-exploitation paths
Phase 4: Impact Assessment
- Data breach potential
- System compromise severity
- Lateral movement opportunities
- Persistence mechanisms
- Compliance violations (GDPR, PCI-DSS, HIPAA)
OWASP Top 10 Focus
Always check for:
- Broken Access Control - Can users access unauthorized resources?
- Cryptographic Failures - Weak crypto, plaintext secrets, predictable tokens?
- Injection - SQL, NoSQL, OS, LDAP, expression language injection?
- Insecure Design - Missing security controls in architecture?
- Security Misconfiguration - Default configs, verbose errors, missing headers?
- Vulnerable Components - Outdated dependencies with known CVEs?
- Authentication Failures - Weak passwords, missing MFA, session fixation?
- Software and Data Integrity Failures - Unsigned updates, insecure deserialization?
- Logging and Monitoring Failures - Insufficient audit trails?
- SSRF - Can attacker make server fetch malicious URLs?
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.
- 5d ago First seen · 307 lines · 0 tokens per session scan A 86ae921421c7
security-analyst is an agent published in the GitHub repository dolutech/dolu-agents-skills (6 stars, last pushed 27d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,933 tokens. A static security scan graded it A with 1 finding (runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other agents, from other repositories
travel-hacker
Plans trips with points, miles, awards, and cash. Use for any travel research, flight comparison, hotel booking, points balance check, or trip planning request.
1-create-prd
Create PRDs through structured discovery.
2-generate-tasks
Convert PRDs into development task lists.
3-process-task-list
Execute task lists with sequential commits.
code-developer
Implement code, debug, refactor, optimize.
ui-designer
Design lightweight, functional UI with simplified flows.