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 Kaademos/secure-sdlc-agentsnpx agentmods add plugins/kaademos/secure-sdlc-agents/marketplacegit clone --depth 1 https://github.com/Kaademos/secure-sdlc-agentsWrote 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/kaademos/secure-sdlc-agents/marketplace)<a href="https://agentmods.dev/plugins/kaademos/secure-sdlc-agents/marketplace"><img src="https://agentmods.dev/badge/plugins/kaademos/secure-sdlc-agents/marketplace.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
secure-sdlc-agents marketplace 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 4d 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.
What it actually says
{
"name": "secure-sdlc-agents",
"owner": {
"name": "Kaademos",
"email": "[email protected]"
},
"metadata": {
"description": "A team of 8 AI security specialists embedded in your coding workflow — covering every phase of the Secure SDLC from requirements to release gating.",
"version": "1.3.2"
},
"plugins": [
{
"name": "secure-sdlc-agents",
"source": {
"source": "github",
"repo": "Kaademos/secure-sdlc-agents"
},
"description": "8 AI security specialist agents for the full Secure SDLC: threat modelling, AppSec, GRC, IaC review, AI/LLM security, and release gating. Works with Claude Code, Cursor, Windsurf, and any MCP-compatible tool.",
"version": "1.3.2",
"author": {
"name": "Kaademos"
},
"homepage": "https://github.com/Kaademos/secure-sdlc-agents",
"repository": "https://github.com/Kaademos/secure-sdlc-agents",
"license": "MIT",
"keywords": [
"security",
"appsec",
"sdlc",
"owasp",
"asvs",
"compliance",
"threat-modeling",
"secure-coding",
"devsecops",
"grc"
],
"category": "security",
"tags": [
"security",
"appsec",
"devsecops",
"owasp",
"compliance",
"threat-modeling",
"agent-skills"
],
"strict": true
}
]
}
The plugins it lists here
This marketplace lists 1 plugin kept in the same repository. Each has its own page, its own measurements and its own install command.
What ships with it
1 file beside marketplace.json in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 4d ago First seen · 52 lines scan A 6f8823d5cce8
secure-sdlc-agents marketplace is a plugin published in the GitHub repository Kaademos/secure-sdlc-agents (13 stars, last pushed 1mo ago), licensed MIT. 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-08-30.
Other plugins, from other repositories
web-app-security-skill
Audit and harden authorized Web projects with explainable, reproducible evidence.
websec-validator
Defensive, local-first security recon that briefs your AI coding agent on your OWN codebase. Read-only by default: facts + tailored probes + a calibrated findings ledger, code-in / artifacts-out, no LLM / no server / no running app. Live probes are opt-in against a TEST instance you own; production is out of scope.
claude-cybersecurity
AI-powered cybersecurity code review with 8 specialist agents, OWASP Top 10:2021, CWE Top 25:2024, MITRE ATT&CK v15, and framework-aware false-positive suppression.
Claude-BugHunter
82-skill bug-hunting & external red-team bundle for Claude Code — 57 hunt- web/vuln-class + framework skills, enterprise platform attack chains (M365/Entra, Okta, SharePoint, vCenter, SSL-VPN, APK/iOS), recon/OSINT, reporting & validation gates, and Burp MCP integration. Skills auto-load by topic; 15 slash commands in.
oswe
Deep white-box OSWE-style web app security audit via /oswe:audit (PHP, Node.js, Python, Java, .NET) — Markdown + visual HTML reports. By Laucked Security.
ai-app-security
Security guardrails for AI-built apps: OWASP/API/LLM/MCP rules applied while building, an /audit skill for full reviews, and a hook that blocks secret commits.