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 beel-collab/presets.dev --skill security-compliance-compliance-checkgit clone --depth 1 https://github.com/beel-collab/presets.devWrote 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/beel-collab/presets.dev/security-compliance-compliance-check)<a href="https://agentmods.dev/skills/beel-collab/presets.dev/security-compliance-compliance-check"><img src="https://agentmods.dev/badge/skills/beel-collab/presets.dev/security-compliance-compliance-check/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/beel-collab/presets.dev/security-compliance-compliance-check"><img src="https://agentmods.dev/badge/skills/beel-collab/presets.dev/security-compliance-compliance-check.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.00044 | $0.00536 |
| Opus 5 | $0.00022 | $0.00268 |
| Sonnet 5 | $0.00009 | $0.00107 |
| Haiku 4.5 | $0.00004 | $0.00054 |
Grade A, and why
security-compliance-compliance-check 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 5d 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.
This is a copy
89% identical to security-compliance-compliance-check — 15 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Regulatory Compliance Check
You are a compliance expert specializing in regulatory requirements for software systems including GDPR, HIPAA, SOC2, PCI-DSS, and other industry standards. Perform comprehensive compliance audits and provide implementation guidance for achieving and maintaining compliance.
Use this skill when
- Assessing compliance readiness for GDPR, HIPAA, SOC2, or PCI-DSS
- Building control checklists and audit evidence
- Designing compliance monitoring and reporting
Do not use this skill when
- You need legal counsel or formal certification
- You do not have scope approval or access to required evidence
- You only need a one-off security scan
Context
The user needs to ensure their application meets regulatory requirements and industry standards. Focus on practical implementation of compliance controls, automated monitoring, and audit trail generation.
Requirements
$ARGUMENTS
Instructions
- Clarify goals, constraints, and required inputs.
- Apply relevant best practices and validate outcomes.
- Provide actionable steps and verification.
- If detailed examples are required, open
resources/implementation-playbook.md.
Safety
- Avoid claiming compliance without a formal audit.
- Protect sensitive data and limit access to audit artifacts.
Output Format
- Compliance Assessment: Current compliance status across all applicable regulations
- Gap Analysis: Specific areas needing attention with severity ratings
- Implementation Plan: Prioritized roadmap for achieving compliance
- Technical Controls: Code implementations for required controls
- Policy Templates: Privacy policies, consent forms, and notices
- Audit Procedures: Scripts for continuous compliance monitoring
- Documentation: Required records and evidence for auditors
- Training Materials: Workforce compliance training resources
Focus on practical implementation that balances compliance requirements with business operations and user experience.
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.
- 5d ago First seen · 65 lines · 44 tokens per session scan A d4988d86a49e
security-compliance-compliance-check is a skill published in the GitHub repository beel-collab/presets.dev (3 stars, last pushed 4mo ago), licensed MIT. It adds 44 tokens to every session and 536 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 89% identical to security-compliance-compliance-check, differing in 15 lines, and is treated as a copy.
Other skills, from other repositories
godot-export
Export and build a Godot 4.7 project for distribution: install export templates, define export presets (Windows/macOS/Linux/Web/Android), run headless command-line exports for CI, and handle web (HTML5) COOP/COEP and dedicated-server/headless builds. Use when exporting a Godot game, configuring exportpresets.cfg…
unity-build-pipeline
Build and ship Unity 6.3 LTS players: build settings and scenes, player/quality settings, the IL2CPP vs Mono scripting backend, managed code stripping, scripted BuildPipeline.BuildPlayer, and CI/headless builds. Use when configuring or automating a build, choosing a scripting backend, shrinking build size, or when the…
skill-creator-primer
You MUST load this skill before the skill-creator skill AND before making ANY change to, or conducting a review of ANY Agent Skill. Triggers include creating, editing, reviewing, or contributing to any part of an Agent Skill (description, frontmatter, body, references, scripts, trigger evals, conflicts, etc).
llm-wiki
Use when building or maintaining a self-contained personal knowledge base (an LLM wiki) in plain markdown. Triggers: ingesting sources into a wiki, querying wiki knowledge, linting wiki health, auditing article claims against their sources, critiquing a wiki source's reasoning, superseding stale knowledge, 'add to…
extract-wisdom
Extract wisdom, insights, and actionable takeaways from YouTube videos, blog posts, articles, or text files. Use when asked to extract wisdom or key insights from a given content source.
apply-mantel-styles
Provides guidelines for applying Mantel's brand styles to diagrams and frontend components. Use when asked to create visuals that need to align with Mantel's branding.