security

security is a skill for Claude Code, Codex from whitebeardit/.cursor. It costs 39 tokens per session (1,754 once invoked), scanned A, original, MIT.

A set of secure coding practices covering authentication, permissions, input validation, encryption, password storage, and common OWASP security risks. OWASP is a community project that documents frequent web application vulnerabilities.

In plain words
What is it for?
Use it when building login and permission checks, validating requests, protecting sensitive data, or addressing security vulnerabilities.
Why use it?
It helps prevent problems such as unauthorized access, exposed sensitive data, and unsafe handling of user input.

Skill for Claude CodeCodex

Install

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.

agentmods
npx agentmods add skills/whitebeardit/.cursor/skill-security
Any agent
npx skills add whitebeardit/.cursor --skill skill-security
Clone the repo
git clone --depth 1 https://github.com/whitebeardit/.cursor

Made for: Claude Code, Codex.

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.

agentmods badge for security

README.md
[![agentmods](https://agentmods.dev/badge/skills/whitebeardit/.cursor/skill-security.svg)](https://agentmods.dev/skills/whitebeardit/.cursor/skill-security)
Your own site
<a href="https://agentmods.dev/skills/whitebeardit/.cursor/skill-security"><img src="https://agentmods.dev/badge/skills/whitebeardit/.cursor/skill-security.svg" alt="Measured on agentmods" height="20"></a>
Per session 39 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,754 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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.

ModelPer sessionOnce invoked
Fable 5 $0.00039 $0.01754
Opus 5 $0.00019 $0.00877
Sonnet 5 $0.00008 $0.00351
Haiku 4.5 $0.00004 $0.00175

Measured 3d ago against content hash ef0c7b98cbc8, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

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

skills/shared/skill-security/SKILL.md · 309 lines

How it starts

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

Security Best Practices

This skill provides security best practices, OWASP Top 10 guidance, and secure coding patterns applicable across multiple programming languages.

OWASP Top 10 (2021)

1. Broken Access Control

Problem: Users can access resources they shouldn't have access to.

Solutions:

  • Implement proper authentication and authorization
  • Validate user permissions on every request
  • Use principle of least privilege
  • Validate ownership before allowing access
// ✅ Good: Check authorization
export async function getOrder(req: Request, res: Response) {
  const order = await orderService.getById(req.params.id);
  
  if (order.userId !== req.user.id) {
    return res.status(403).json({ error: 'Forbidden' });
  }
  
  res.json(order);
}

2. Cryptographic Failures

Problem: Sensitive data exposed due to weak encryption or missing encryption.

Solutions:

  • Encrypt sensitive data at rest and in transit
  • Use strong, up-to-date cryptographic algorithms
  • Never store passwords in plain text (use hashing)
  • Use HTTPS/TLS for all communications
// ✅ Good: Hash passwords
import bcrypt from 'bcrypt';

const hashedPassword = await bcrypt.hash(password, 10);

// ✅ Good: Verify passwords
const isValid = await bcrypt.compare(inputPassword, hashedPassword);

3. Injection

Problem: Untrusted data is sent to interpreter (SQL, NoSQL, OS, LDAP).

Solutions:

  • Use parameterized queries/prepared statements
  • Validate and sanitize all input
  • Use ORMs with built-in protection
  • Escape special characters
// ❌ Bad: SQL Injection vulnerability
const query = `SELECT * FROM users WHERE id = ${userId}`;

// ✅ Good: Parameterized query
const query = 'SELECT * FROM users WHERE id = $1';
const result = await db.query(query, [userId]);
// ✅ Good: Parameterized query in C#
var query = "SELECT * FROM Users WHERE Id = @id";
var result = await connection.QueryAsync<User>(query, new { id = userId });

Read the full file on GitHub · 309 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.

  1. 3d ago First seen · 309 lines · 39 tokens per session scan A ef0c7b98cbc8

Subscribe to this mod's changes

security is a skill published in the GitHub repository whitebeardit/.cursor (12 stars, last pushed 6mo ago), licensed MIT. It adds 39 tokens to every session and 1,754 once invoked, about $0.0002 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.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens

chat-perf

Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.

microsoft/vscode · 51 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens