What is security-patterns?

A set of general security guidelines based on the OWASP Top 10, a widely used list of common web application risks. It covers issues such as weak access controls, exposed secrets, unsafe input, and vulnerable dependencies.

It is for reviewing designs and code for common vulnerabilities, including injection, bad authorization, insecure settings, weak encryption, and outdated components.

It gives coding agents a shared checklist for spotting and fixing security problems across frameworks and programming languages. The guidance helps avoid relying on framework-specific assumptions.

How CarlosDanielDev/maestro configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to CarlosDanielDev/maestro. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/CarlosDanielDev/maestro/main/.claude/skills/security-patterns/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/CarlosDanielDev/maestro

Made for: Claude Code.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/carlosdanieldev/maestro/security-patterns/github.svg)](https://agentmods.dev/skills/carlosdanieldev/maestro/security-patterns)

Your own site

<a href="https://agentmods.dev/skills/carlosdanieldev/maestro/security-patterns"><img src="https://agentmods.dev/badge/skills/carlosdanieldev/maestro/security-patterns/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/carlosdanieldev/maestro/security-patterns"><img src="https://agentmods.dev/badge/skills/carlosdanieldev/maestro/security-patterns.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 26 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,769 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00026	$0.01769
Opus 5.5	$0.00010	$0.00708
Sonnet 5.5	$0.00005	$0.00354
Haiku 4.5	$0.00003	$0.00177

Measured 1mo ago against content hash 3ee5552c3e9c, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

security-patterns 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.

.claude/skills/security-patterns/SKILL.md · 264 lines

How it starts

The opening of the file, as written. The whole thing — 264 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Security Patterns

Universal security patterns and OWASP Top 10 compliance. Framework-agnostic security guidance.

Skill Usage

Aspect	Details
Consumer	`subagent-security-analyst` (and all architects)
Purpose	Security vulnerability detection and remediation patterns
Invocation	Subagents read this skill; NOT directly invocable by users
Applicability	All frameworks and languages

OWASP Top 10 (2021) - Quick Reference

#	Vulnerability	Description	Prevention
A01	Broken Access Control	Missing or improper authorization	Implement proper access controls, deny by default
A02	Cryptographic Failures	Weak encryption, exposed secrets	Use strong encryption, protect data at rest/transit
A03	Injection	SQL, NoSQL, Command injection	Use parameterized queries, ORM, input validation
A04	Insecure Design	Missing security requirements	Apply threat modeling, secure design patterns
A05	Security Misconfiguration	Default configs, verbose errors	Harden configs, disable debug in production
A06	Vulnerable Components	Outdated dependencies	Keep dependencies updated, scan for CVEs
A07	Auth/Session Issues	Weak authentication	Use MFA, secure session management, strong passwords
A08	Data Integrity Failures	Unsigned/unverified data	Implement digital signatures, integrity checks
A09	Logging Failures	Insufficient logging	Log security events, monitor anomalies
A10	SSRF	Server-side request forgery	Validate URLs, use allowlists, network segmentation

Common Security Patterns

Input Validation

ALWAYS validate and sanitize user input:
1. Validate type, length, format, range
2. Use allowlist (not denylist) when possible
3. Sanitize before processing or storing
4. Encode before rendering (prevent XSS)

Authentication

Read the full file on GitHub · 264 lines

Changes

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 · 264 lines · 26 tokens per session scan A 3ee5552c3e9c

Subscribe to this mod's changes

security-patterns is a skill published in the GitHub repository CarlosDanielDev/maestro (31 stars, last pushed 20d ago), licensed MIT. It adds 26 tokens to every session and 1,769 once invoked, about $0.0001 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-10-02.