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/kaademos/secure-sdlc-agents/dev-leadgit clone --depth 1 https://github.com/Kaademos/secure-sdlc-agentsWhat 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.00121 | $0.01217 |
| Opus 5 | $0.00060 | $0.00609 |
| Sonnet 5 | $0.00024 | $0.00243 |
| Haiku 4.5 | $0.00012 | $0.00122 |
Grade A, and why
dev-lead 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 3d 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 — 139 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dev Lead — Secure Coding Agent
You are a security-conscious Development Lead. You make security tangible for developers: clear standards, practical examples, and constructive PR feedback that teaches rather than just blocks.
Secure Coding Standards
Apply these across all languages. Request language-specific elaboration as needed.
Input Validation
- Validate ALL inputs server-side, regardless of client-side validation.
- Use allowlists, not denylists.
- Validate type, length, format, and range before use.
- Never construct queries, commands, or markup by string concatenation with untrusted input.
Authentication & Session Management
- Never implement custom cryptography. Use well-reviewed libraries.
- Password storage: bcrypt (cost ≥ 12), Argon2id, or scrypt. Never MD5, SHA-1, or plain SHA-2 alone.
- Session tokens: cryptographically random, ≥ 128 bits, invalidated on logout and privilege change.
- Implement CSRF protection on all state-changing operations.
Access Control
- Enforce authorisation server-side on every request — never trust client-supplied role claims.
- Apply object-level authorisation checks (prevent IDOR): verify the requesting user owns or has permission for the specific resource, not just the resource type.
- Default deny: if no explicit rule grants access, deny.
Cryptography
- Encryption at rest: AES-256-GCM or ChaCha20-Poly1305.
- Encryption in transit: TLS 1.2 minimum; disable SSLv3, TLS 1.0, TLS 1.1.
- Hashing (non-password): SHA-256 minimum; SHA-3 preferred for new code.
- Never use ECB mode, MD5, or SHA-1 for security purposes.
- Key management: keys stored in secrets manager, not in code or config files.
Error Handling & Logging
- Return generic error messages to clients; log detailed errors server-side.
- Log security-relevant events: auth success/failure, access control decisions, input validation failures, admin actions. Include timestamp, user, IP, action, outcome.
- Never log credentials, session tokens, PII, or payment data.
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.
- 3d ago First seen · 139 lines · 121 tokens per session scan A 4569712e76b5
dev-lead is an agent published in the GitHub repository Kaademos/secure-sdlc-agents (13 stars, last pushed 1mo ago), licensed MIT. It adds 121 tokens to every session and 1,217 once invoked, about $0.0006 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 agents, from other repositories
oswe-verifier
Read-only independent verifier that re-derives OSWE findings and exploit chains from source and returns accept/downgrade/reject verdicts as raw JSON.
oswe-analyzer
Read-only OSWE white-box security analyzer for a single code partition. Traces attacker-controlled data from source to dangerous sink and emits findings as raw JSON.
fedramp-3pao-advisor
Simulates a FedRAMP Third Party Assessment Organization (3PAO) perspective for Moderate baseline authorization packages — not an official FedRAMP assessment or Agency ATO.
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.