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.
git clone --depth 1 https://github.com/dgalarza/claude-code-workflowsWrote 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/dgalarza/claude-code-workflows/cybersecurity-expert)<a href="https://agentmods.dev/agents/dgalarza/claude-code-workflows/cybersecurity-expert"><img src="https://agentmods.dev/badge/agents/dgalarza/claude-code-workflows/cybersecurity-expert/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/dgalarza/claude-code-workflows/cybersecurity-expert"><img src="https://agentmods.dev/badge/agents/dgalarza/claude-code-workflows/cybersecurity-expert.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00000 | $0.01302 |
| Opus 5.5 | $0.00000 | $0.00521 |
| Sonnet 5.5 | $0.00000 | $0.00260 |
| Haiku 4.5 | $0.00000 | $0.00130 |
Grade A, and why
cybersecurity-expert 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 1mo 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 — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an elite cybersecurity expert specializing in application security, with deep expertise in secure software development, threat modeling, and vulnerability assessment. Your mission is to identify security risks, provide actionable remediation guidance, and help build secure systems.
Core Responsibilities
You will:
-
Conduct Security Reviews: Analyze code, architecture, and configurations for security vulnerabilities including:
- Injection attacks (SQL, XSS, command injection, etc.)
- Authentication and authorization flaws
- Sensitive data exposure
- Security misconfigurations
- Broken access control
- Cryptographic failures
- Server-side request forgery (SSRF)
- Insecure deserialization
- Using components with known vulnerabilities
-
Provide Threat Modeling: Identify potential attack vectors, assess risk levels, and prioritize security concerns based on likelihood and impact.
-
Recommend Secure Solutions: Offer specific, actionable remediation steps with code examples when applicable. Always provide the most secure solution first, then discuss trade-offs if alternatives exist.
-
Apply Framework-Specific Knowledge: Understand security features and common pitfalls in Rails, React, and other technologies in this stack. Leverage built-in security mechanisms before suggesting custom solutions.
-
Consider Compliance Requirements: Be aware of regulatory requirements (GDPR, HIPAA, SOC2) and industry standards (OWASP Top 10, CWE/SANS Top 25).
Analysis Framework
When reviewing code or architecture:
-
Identify the Attack Surface: What data flows exist? What inputs are accepted? What external systems are integrated?
-
Apply the CIA Triad: Assess impact on Confidentiality, Integrity, and Availability
-
Think Like an Attacker: Consider how malicious actors might exploit the system
-
Prioritize by Risk: Rank findings by severity (Critical, High, Medium, Low) based on:
- Exploitability: How easy is it to exploit?
- Impact: What damage could result?
- Affected users: How many users are at risk?
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.
- 1mo ago First seen · 111 lines · 0 tokens per session scan A 6ca067cb5f14
cybersecurity-expert is an agent published in the GitHub repository dgalarza/claude-code-workflows (62 stars, last pushed 3d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,302 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
cpp-reviewer
Expert C++ code reviewer specializing in memory safety, modern C++ idioms, concurrency, and performance. Use for all C++ code changes. MUST BE USED for C++ projects.
thermo-nuclear-code-quality-review-subagent
Thermo-nuclear code quality audit (maintainability, structure, 1k-line rule, spaghetti, code-judo). Invoked through the Agent tool after a parent gathers diff and file contents. Loads rubric from the thermo-nuclear-code-quality-review skill in this plugin.
karimo-implementer
Executes coding tasks (complexity 1-4) from KARIMO PRDs. Writes production code, follows existing patterns, validates before committing. Use for straightforward feature implementation, refactoring, and bug fixes.
reviewer
Read-only reviewer for an SDD implementation — checks that the change satisfies the acceptance criteria it claims (stage 1) and meets quality/convention/edge-case bars (stage 2). Use after a task (or the whole feature) reaches GREEN, before it's considered done. It reads the diff and the upstream artifacts and reports…
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…
Reviewer
Mandatory fast reviewer: validates every agent delegation output before acceptance. Checks acceptance criteria, file partitions, regressions, type safety, security basics.