security-and-compliance

security-and-compliance is a skill for Claude Code from aneja5/forge-skills. It costs 70 tokens per session (1,534 once invoked), scanned A, original, MIT.

A review of an application's security risks, sensitive data, trust boundaries, and compliance obligations. It covers requirements such as GDPR and SOC 2, which are privacy and security standards.

In plain words
What is it for?
Use it to prepare for audits, assess risks before release, create a threat model, and plan protections for data stores and access boundaries.
Why use it?
It helps find security and regulatory gaps before launch, audits, or incidents, especially when the system stores personal or customer data.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the forge-skills plugin — 42 skills, 36 commands, 1 hook shipped together

Good fit Use it to prepare for audits, assess risks before release, create a threat model, and plan protections for data stores and access boundaries.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/aneja5/forge-skills/security-and-compliance
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.

Any agent
npx skills add aneja5/forge-skills --skill security-and-compliance
Clone the repo
git clone --depth 1 https://github.com/aneja5/forge-skills

Made for: Claude Code.

Or install forge-skills, the plugin that ships this one along with the rest of its 42 skills, 36 commands, 1 hook.

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-and-compliance

README.md
[![agentmods](https://agentmods.dev/badge/skills/aneja5/forge-skills/security-and-compliance/github.svg)](https://agentmods.dev/skills/aneja5/forge-skills/security-and-compliance)
Your own site
<a href="https://agentmods.dev/skills/aneja5/forge-skills/security-and-compliance"><img src="https://agentmods.dev/badge/skills/aneja5/forge-skills/security-and-compliance/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.

agentmods 80×15 button for security-and-compliance

Your own site · 80×15
<a href="https://agentmods.dev/skills/aneja5/forge-skills/security-and-compliance"><img src="https://agentmods.dev/badge/skills/aneja5/forge-skills/security-and-compliance.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 70 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,534 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00070 $0.01534
Opus 5 $0.00035 $0.00767
Sonnet 5 $0.00014 $0.00307
Haiku 4.5 $0.00007 $0.00153

Measured 7d ago against content hash 71d3f2df9d0b, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

security-and-compliance 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 7d 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/security-and-compliance/SKILL.md · 135 lines

How it starts

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

Security and Compliance

Overview

Read .forge/architecture.md and .forge/contracts/ to produce .forge/security.md — a comprehensive security and compliance assessment. The output must identify every data store, every trust boundary, and every regulatory requirement before any code is written.

When to Use

  • .forge/architecture.md exists and the system handles user data
  • Regulatory requirements apply (GDPR, CCPA, SOC 2, HIPAA, PCI-DSS)
  • System has multi-tenant data or PII
  • Pre-launch security gate or investor due diligence

When NOT to Use

  • No architecture exists — run architecture-and-contracts first
  • Looking for code-level vulnerabilities — use code-review-and-quality security axis
  • Emergency security incident — that's incident response, not planning

Common Rationalizations

Thought Reality
"We'll handle security after MVP" Security retrofits cost 10x. Design it in now
"We don't have PII" Email addresses are PII. User IDs linked to behavior are PII. Audit first
"Our cloud provider handles compliance" Shared responsibility model — your provider secures infra, you secure data and access
"SOC 2 is only for enterprise sales" Any B2B buyer with a security team will ask. Start the roadmap early
"Encryption at rest is enough" Encryption without key management is theater. Who holds the keys?

Red Flags

  • No data classification scheme (what's sensitive vs. public)
  • Multi-tenant system with no Row-Level Security or tenant isolation plan
  • PII inventory is empty ("we don't store PII" without audit)
  • Vendor list has no security assessment
  • Threat model is missing or covers fewer than 5 attack vectors
  • "We'll encrypt everything" without specifying what, how, and who manages keys

Core Process

Step 1: Authentication model

Define: identity provider, session management, token format, expiry policy, MFA requirements, credential storage. Map auth flow for every user type in the PRD.

Read the full file on GitHub · 135 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. 7d ago First seen · 135 lines · 70 tokens per session scan A 71d3f2df9d0b

Subscribe to this mod's changes

security-and-compliance is a skill published in the GitHub repository aneja5/forge-skills (3 stars, last pushed 3mo ago), licensed MIT. It adds 70 tokens to every session and 1,534 once invoked, about $0.0003 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-09-03.