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.
/plugin marketplace add jassics/awesome-claude-securitynpx agentmods add plugins/jassics/awesome-claude-security/security-engineergit clone --depth 1 https://github.com/jassics/awesome-claude-securityWrote 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/plugins/jassics/awesome-claude-security/security-engineer)<a href="https://agentmods.dev/plugins/jassics/awesome-claude-security/security-engineer"><img src="https://agentmods.dev/badge/plugins/jassics/awesome-claude-security/security-engineer.svg" alt="Measured on agentmods" height="20"></a>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 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.
The source is not reproduced here
Licensed GPL-3.0
The repository is licensed GPL-3.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.
What it installs
The manifest is a name and a version. 1 skill, 1 command, 1 agent travel with it, and installing the plugin installs all of them — 154 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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 · 11 lines scan A 3c074563a5df
security-engineer is a plugin published in the GitHub repository jassics/awesome-claude-security (6 stars, last pushed 29d ago), licensed GPL-3.0. Its token cost is not measured: this kind of file is read by the harness, not the model. 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-03.
Other plugins, from other repositories
platform-skills
Practical guidance for platform engineers across Claude, Codex, Cursor, and Copilot: Kubernetes (baseline, RBAC, workload hardening, debug), GitHub Actions (design, security, review, debug), Azure (Workload Identity, tagging, AKS, RBAC), OpenShift (SCC, Routes, GitOps, upgrades), Secrets (ESO, Sealed Secrets, rotation.
infrastructure
Infrastructure and DevOps specialists for AWS, GCP, Kubernetes, Docker, Terraform, GitHub Actions, GitLab CI, and security auditing.
ship
Complete PR workflow from commit to production with validation.
ground
Ground Control for Claude Code.
repo-agent-harness
Lay the foundation that makes a repository teach coding agents how to work in it: delivery moments wired to hooks, a layered docs truth source, CI gates plus tool-call guards, a rebuildable repo graph, and a consolidation pass. Bootstraps once, then the repo stands on its own.
claudeconf
Research-driven, technology-agnostic harness generator for Claude Code: pinned, standard-tool quality + security pipelines (git hooks, CI, e2e, gates, supply-chain admission, agent-hardening) plus a read-only harness-doctor agent.