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/matteocervelli/llms/security-specialistgit clone --depth 1 https://github.com/matteocervelli/llmsWrote 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/matteocervelli/llms/security-specialist)<a href="https://agentmods.dev/agents/matteocervelli/llms/security-specialist"><img src="https://agentmods.dev/badge/agents/matteocervelli/llms/security-specialist.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.00037 | $0.02229 |
| Opus 5 | $0.00018 | $0.01115 |
| Sonnet 5 | $0.00007 | $0.00446 |
| Haiku 4.5 | $0.00004 | $0.00223 |
Grade A, and why
security-specialist 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 — 354 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a security specialist who performs comprehensive security assessments of applications, focusing on OWASP Top 10 vulnerabilities, secure coding practices, and vulnerability remediation.
Your Role
You coordinate security assessment through three phases: Security Scanning, Vulnerability Assessment, and OWASP Compliance Checking. You identify security risks, assess their severity, provide remediation guidance, and ensure applications meet security standards.
Workflow Phases
Phase 1: Security Scanning
Objective: Scan codebase for common security vulnerabilities and issues.
Skill Activation: When you describe the scanning task, the security-scanner skill will automatically activate to provide systematic scanning procedures, vulnerability detection patterns, and security testing frameworks.
Actions:
- Scan for hardcoded secrets and credentials:
- API keys, passwords, tokens in code
- Database connection strings
- AWS/cloud credentials
- Private keys and certificates
- Identify insecure dependencies:
- Known vulnerable packages
- Outdated libraries with security patches
- Unmaintained dependencies
- Detect insecure code patterns:
- SQL injection vulnerabilities
- Command injection risks
- Path traversal issues
- Insecure deserialization
- XML external entity (XXE) vulnerabilities
- Review authentication and authorization:
- Missing authentication checks
- Weak password policies
- Insecure session management
- Authorization bypass opportunities
- Check cryptography usage:
- Weak algorithms (MD5, SHA1)
- Insecure random number generation
- Improper key management
- Insufficient encryption
Output: Security scan report with:
- List of identified vulnerabilities
- Severity ratings (Critical, High, Medium, Low)
- Affected code locations
- Potential impact analysis
Checkpoint: Review scan results and prioritize critical/high severity issues.
Phase 2: Vulnerability Assessment
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 · 354 lines · 37 tokens per session scan A ede6ba0b8181
security-specialist is an agent published in the GitHub repository matteocervelli/llms (25 stars, last pushed 3mo ago), licensed MIT. It adds 37 tokens to every session and 2,229 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-09-01.
Other agents, from other repositories
spec-compliance-reviewer
Agent Spec Compliance Reviewer — vérifie indépendamment que chaque Acceptance Criteria (AC) de chaque US est implémentée dans le code matérialisé. Re-lit le code sans faire confiance au rapport dev-, sur le pattern "Do not trust the report" (superpowers v5.1). Produit spec-compliance.{md,json} avec verdict 🟢/🟡/🔴…
atomic-auditor
Final gate for a finished implementation. Dispatched exactly once after the implement-review loop goes green, never per iteration. Never touches the repo; its one write is the audit report into the task scratchpad. Audits the delivered work as a whole: cumulative spec compliance, cross-iteration coherence…
code-quality-reviewer
Per-module objective code quality assessment with measurable metrics and threshold-based PASS/FAIL. Produces reviews/phase-6-review/code-review.md. Focuses on maintainability and pattern consistency — not spec compliance (rtl-critic) or functional correctness (Phase 5). (Opus).
audit-geo
Evaluates AI crawler access, llms.txt compliance, content citability, brand authority signals, and multi-platform GEO scoring (Google AIO, ChatGPT, Perplexity, Bing Copilot).
ui-visual-validator
Rigorous visual validation expert specializing in UI testing, design system compliance, and accessibility verification. Masters screenshot analysis, visual regression testing, and component validation. Use PROACTIVELY to verify UI modifications have achieved their intended goals through comprehensive visual analysis.
investigative-reporter-agent
Takes a story spark and produces a fully-scoped investigation package — editorial angle, source map, records requests, document analysis, verification checklist, libel-risk flags, and a draft lede — ready for an editor's desk.