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 skills add Kaademos/secure-sdlc-agents --skill security-and-hardeninggit 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/skills/kaademos/secure-sdlc-agents/security-and-hardening)<a href="https://agentmods.dev/skills/kaademos/secure-sdlc-agents/security-and-hardening"><img src="https://agentmods.dev/badge/skills/kaademos/secure-sdlc-agents/security-and-hardening/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/skills/kaademos/secure-sdlc-agents/security-and-hardening"><img src="https://agentmods.dev/badge/skills/kaademos/secure-sdlc-agents/security-and-hardening.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.00046 | $0.01211 |
| Opus 5 | $0.00023 | $0.00606 |
| Sonnet 5 | $0.00009 | $0.00242 |
| Haiku 4.5 | $0.00005 | $0.00121 |
Grade A, and why
security-and-hardening scanned grade A with 1 finding 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 11d 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.
Runs shell commandslowCapability
Expected in a hook, worth knowing in a rule or an instructions file.
- Any `eval()`, `exec()`, `subprocess.run(shell=True)` with user-controlled data How it starts
The opening of the file, as written. The whole thing — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Security and Hardening
Overview
This skill enforces the secure coding standards and PR review discipline that prevent the most common vulnerability classes from reaching production. It covers OWASP Top 10 categories, ASVS control requirements, and the review process that catches issues before they merge — not after they breach.
When to Use
- Any code handling user-supplied input (forms, APIs, file uploads, query params)
- Authentication, session management, or access control changes
- Cryptographic operations — hashing, encryption, key management
- Dependency additions or upgrades
- Pull request review on any security-sensitive component
- SAST finding triage and remediation
Process
Step 1 — Classify the security surface
Before reviewing, identify which categories are in scope:
| Surface | Key risks |
|---|---|
| Input handling | Injection (SQL, LDAP, OS command, template, XSS) |
| Authentication | Weak passwords, missing MFA, session fixation |
| Access control | IDOR, broken object-level auth, privilege escalation |
| Cryptography | Weak algorithms, hardcoded keys, improper key storage |
| File handling | Path traversal, type confusion, SVG XSS, unrestricted upload |
| Dependencies | Known CVEs, unmaintained packages, licence risk |
| Error handling | Stack trace leakage, verbose error messages |
Step 2 — Apply the PR security checklist
- No hardcoded secrets, API keys, or credentials anywhere in the diff
- All user-controlled inputs validated server-side (type, length, format, range)
- SQL/NoSQL queries use parameterised statements — no string concatenation with input
- Object-level authorisation checks present (not just resource-type checks)
- New dependencies reviewed: CVE status, maintenance activity, licence, download count
- Error messages returned to the client are generic; detail is server-side only
- Log entries do not include PII, credentials, session tokens, or payment data
- Cryptographic operations use approved algorithms (AES-256-GCM, Argon2id, SHA-256+)
- File upload handlers validate MIME type, magic bytes, size, and destination path
- ASVS requirements from
docs/security-requirements.mdare satisfied
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.
- 11d ago First seen · 118 lines · 46 tokens per session scan A f6a0b92812f3
security-and-hardening is a skill published in the GitHub repository Kaademos/secure-sdlc-agents (13 stars, last pushed 1mo ago), licensed MIT. It adds 46 tokens to every session and 1,211 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
secrets-gitleaks
Hardcoded secret detection and prevention in git repositories and codebases using Gitleaks. Identifies passwords, API keys, tokens, and credentials through regex-based pattern matching and entropy analysis. Use when: (1) Scanning repositories for exposed secrets and credentials, (2) Implementing pre-commit hooks to…
speckit-implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
speckit-plan
Execute the implementation planning workflow using the plan template to generate design artifacts.
speckit-specify
Create or update the feature specification from a natural language feature description.
speckit-clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
speckit-tasks
Generate an actionable, dependency-ordered tasks.md for the feature based on available design artifacts.