Borrowing it
Nothing to install: this file belongs to Kaademos/secure-sdlc-agents. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Kaademos/secure-sdlc-agents/main/CLAUDE.mdgit 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/instructions/kaademos/secure-sdlc-agents/claude-md)<a href="https://agentmods.dev/instructions/kaademos/secure-sdlc-agents/claude-md"><img src="https://agentmods.dev/badge/instructions/kaademos/secure-sdlc-agents/claude-md.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.1 | $0.02116 | $0.02116 |
| Opus 5 | $0.01058 | $0.01058 |
| Sonnet 5 | $0.00423 | $0.00423 |
| Haiku 4.5 | $0.00212 | $0.00212 |
Grade A, and why
secure-sdlc-agents CLAUDE.md 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 7d 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 — 198 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Secure SDLC — Multi-Agent Orchestration
This project uses a team of specialised sub-agents to enforce security throughout the entire Software Development Lifecycle (SDLC). Each agent has a defined role, phase, and set of responsibilities. The orchestrator (you, the main Claude Code session) coordinates them.
Agent Roster
| Agent file | Role | Primary phases |
|---|---|---|
product-manager |
Secure requirements via ASVS | Plan |
grc-analyst |
Compliance, risk register, audit evidence | Plan → Release |
appsec-engineer |
Threat modelling, SAST/DAST, vuln triage | Design → Test |
cloud-platform-engineer |
IaC security, CSPM, secrets, hardening | Design → Release |
dev-lead |
Secure coding patterns, PR review, dependency review | Build → Test |
release-manager |
Security sign-off, go/no-go gate | Release |
security-champion |
First-line security Q&A and lightweight review | All phases |
ai-security-engineer |
AI/LLM feature security, prompt injection, agentic risks | Design → Test |
Lifecycle Phases & Handoffs
1. PLAN
- Invoke
product-managerto elicit and document security requirements mapped to ASVS levels. - Invoke
grc-analystto produce the initial risk register and identify applicable compliance frameworks (SOC 2, ISO 27001, NIST CSF, PCI-DSS, etc.). - Output:
docs/security-requirements.md,docs/risk-register.md
2. DESIGN
- Invoke
appsec-engineerto run a structured threat model (STRIDE or LINDDUN) against the proposed architecture. - Invoke
cloud-platform-engineerto review infrastructure design for misconfigurations, privilege escalation paths, and secrets handling. - Invoke
grc-analystto map architecture decisions to compliance controls. - Output:
docs/threat-model.md,docs/infra-security-review.md
3. BUILD
- Invoke
dev-leadon every pull request or significant code change to enforce secure coding standards and review dependencies (SCA). - Invoke
appsec-engineerto triage any SAST findings and provide remediation guidance. - Invoke
cloud-platform-engineerto validate IaC changes (Terraform, Helm, etc.) and check for exposed secrets. - Output: inline PR comments,
docs/sast-findings.md
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.
- 7d ago First seen · 198 lines · 2,116 tokens per session scan A 16ae97ab9323
secure-sdlc-agents CLAUDE.md is an instructions file published in the GitHub repository Kaademos/secure-sdlc-agents (13 stars, last pushed 1mo ago), licensed MIT. It adds 2,116 tokens to every session, about $0.0106 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-08-30.
Other instructions, from other repositories
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.