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 mfkocalar/OWASP-Security-Skills --skill secure-coding-practicesgit clone --depth 1 https://github.com/mfkocalar/OWASP-Security-SkillsWrote 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/mfkocalar/owasp-security-skills/secure-coding-practices)<a href="https://agentmods.dev/skills/mfkocalar/owasp-security-skills/secure-coding-practices"><img src="https://agentmods.dev/badge/skills/mfkocalar/owasp-security-skills/secure-coding-practices/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/mfkocalar/owasp-security-skills/secure-coding-practices"><img src="https://agentmods.dev/badge/skills/mfkocalar/owasp-security-skills/secure-coding-practices.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.00160 | $0.02463 |
| Opus 5.5 | $0.00064 | $0.00985 |
| Sonnet 5.5 | $0.00032 | $0.00493 |
| Haiku 4.5 | $0.00016 | $0.00246 |
Grade A, and why
secure-coding-practices 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 1mo 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 — 257 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OWASP Secure Coding Practices Audit
This skill turns Claude into a rigorous auditor that applies the OWASP Secure Coding Practices (SCP) checklist — derived from OWASP's living sources (Developer Guide, Cheat Sheet Series, Proactive Controls), with the original SCP Quick Reference Guide as its archived historical origin — to evaluate code quality and security posture, grounds every finding in observable evidence, and produces a structured, actionable compliance report.
When this skill applies
Any request that asks Claude to evaluate code against secure coding practices, conduct compliance audits, or harden code: SCP reviews, secure coding audits, compliance checks, "does this follow best practices?" questions. Also trigger when the user pastes code involving data handling, input processing, authentication, database operations, file management, or cryptography without explicitly mentioning security. That's when the value is highest.
How to use this skill
This skill provides two main workflows:
- Quick Audit — for snippets and individual functions (5-50 lines)
- Comprehensive Audit — for files, directories, or full codebases
Both reference the OWASP SCP checklist organized into 14 domains:
- Input validation
- Output encoding
- Authentication and password management
- Session management
- Access control
- Cryptographic practices
- Error handling and logging
- Data protection
- Communication security
- System configuration
- Database security
- File management
- Memory management
- General coding practices
Audit workflow
Run these steps in order. Skipping ahead means you missed context.
1. Scope the review
Pin down three things before reading any code:
- Target: snippet, file, directory, or repo? A 30-line paste and an
audit of
backend/need different shapes. Ask if unclear. - Stack: language, framework, runtime. A SCP finding in Django reads different from one in raw SQL or C.
- Threat context: internet-facing, internal-only, or library? High-trust vs. low-trust boundaries change which checklist items are critical.
What ships with it
7 files beside SKILL.md 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.
- 1mo ago First seen · 257 lines · 160 tokens per session scan A 874c91df4dbb
secure-coding-practices is a skill published in the GitHub repository mfkocalar/OWASP-Security-Skills (3 stars, last pushed 20d ago), licensed MIT. It adds 160 tokens to every session and 2,463 once invoked, about $0.0006 per session on Opus 5.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-31.
Other skills, from other repositories
owasp-security
Reviews code for security vulnerabilities and guides secure implementation using OWASP Top 10:2025, ASVS 5.0, the OWASP Top 10 for LLM Applications (2026), and the OWASP Top 10 for Agentic Applications (2026). Use when reviewing code or a diff for security issues, implementing authentication, authorization, sessions…
ai-security
Use when building any feature that calls an LLM API, processes user input sent to a model, uses RAG or embeddings, deploys an AI agent with tool access, or makes AI-generated output visible to users or downstream systems.
compliance-and-audit
Use when a project requires a compliance framework mapping, when risks need formal documentation, when audit evidence must be collected, or when producing a compliance attestation before release. Applies to SOC 2, ISO 27001, GDPR, PCI DSS, NIST CSF, and DORA.
threat-modeling
Use when a new feature, architecture, or significant design decision is being made. Run before any code is written. Produces a structured STRIDE threat model and architecture review that feeds directly into security requirements and PR review.
security-and-hardening
Use when writing or reviewing code that handles user input, authentication, access control, cryptography, error handling, file uploads, or dependency management. Also activates when a pull request touches any security-sensitive component.
Mixed-Language Monorepos
This skill should be used when the user is auditing a "polyglot monorepo", "multi-language codebase", "microservices with different languages", "Go + Python + TypeScript", or any codebase with services written in different programming languages. Provides strategies for cross-service security analysis and unified…