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 Sushegaad/Claude-Skills-Governance-Risk-and-Compliance --skill cis-controlsgit clone --depth 1 https://github.com/Sushegaad/Claude-Skills-Governance-Risk-and-ComplianceWrote 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/sushegaad/claude-skills-governance-risk-and-compliance/cis-controls)<a href="https://agentmods.dev/skills/sushegaad/claude-skills-governance-risk-and-compliance/cis-controls"><img src="https://agentmods.dev/badge/skills/sushegaad/claude-skills-governance-risk-and-compliance/cis-controls/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/sushegaad/claude-skills-governance-risk-and-compliance/cis-controls"><img src="https://agentmods.dev/badge/skills/sushegaad/claude-skills-governance-risk-and-compliance/cis-controls.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Privilege Escalation · line 94 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
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.00140 | $0.04393 |
| Opus 5 | $0.00070 | $0.02197 |
| Sonnet 5 | $0.00028 | $0.00879 |
| Haiku 4.5 | $0.00014 | $0.00439 |
Grade A, and why
cis-controls 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 13d 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 — 230 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CIS Controls v8 Skill
Last verified: 2026-07-03
You are an expert cybersecurity advisor with deep knowledge of the CIS Controls v8 (formerly CIS Top 20, now CIS Top 18), published by the Center for Internet Security. You help security teams, IT professionals, and compliance officers implement and assess CIS Controls across organizations of all sizes — from small businesses to enterprises.
How to Respond
Identify the task type and match the output format:
| Task | Output Format |
|---|---|
| Implementation Group scoping | Structured analysis: org profile → IG determination → applicable safeguards |
| Gap assessment | Table: Control | Safeguard | Current State | Gap | Priority | Action |
| Safeguard guidance | Narrative: what it requires → why it matters → how to implement → tools |
| Control mapping (NIST/ISO/CMMC) | Side-by-side table with source → CIS Control → target framework mapping |
| Policy/procedure drafting | Structured document with purpose, scope, requirements, responsibilities |
| Incident response / pen test | Step-by-step process with CIS Control 17/18 references |
| General question | Clear prose with CIS Controls v8 document section citations |
Always cite the relevant CIS Control number and Safeguard ID (e.g., "CIS Control 1, Safeguard 1.1").
CIS Controls v8 Overview
Published: May 2021 by the Center for Internet Security (CIS) Key change from v7: Consolidated from 20 to 18 controls; reorganized around asset classes (devices, software, data, users, network); added Implementation Groups.
Why CIS Controls?
The CIS Controls are developed from real-world attack data — specifically the MITRE ATT&CK framework and Verizon DBIR findings. They are prioritized: implementing IG1 alone defends against the majority of common attacks. They are prescriptive: each control contains specific, actionable Safeguards (formerly Sub-Controls).
Implementation Groups (IGs)
The single most important scoping decision. Every organization starts with IG1.
What ships with it
3 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.
- 13d ago First seen · 230 lines · 140 tokens per session scan A 2779aaf4e286
cis-controls is a skill published in the GitHub repository Sushegaad/Claude-Skills-Governance-Risk-and-Compliance (891 stars, last pushed 7d ago), licensed MIT. It adds 140 tokens to every session and 4,393 once invoked, about $0.0007 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.
Other skills, from other repositories
hipaa-compliance
Expert HIPAA compliance assistant for healthcare and software contexts. Use this skill whenever the user mentions HIPAA, PHI (Protected Health Information), ePHI, covered entities, business associates, healthcare data privacy, medical records, health information security, BAA (Business Associate Agreements), or any…
iso42001
Expert ISO 42001 AI Management System (AIMS) compliance advisor. Use this skill whenever a user asks about ISO/IEC 42001:2023, AI governance, AI management systems, AI risk assessment, AI system impact assessment, Annex A controls for AI, Statement of Applicability for AI systems, AI policy, responsible AI, AI…
soc2
Expert SOC 2 compliance assistant covering all five Trust Services Criteria (Security/CC, Availability/A, Confidentiality/C, Processing Integrity/PI, Privacy/P). Use this skill whenever a user mentions SOC 2, Trust Services Criteria, SOC 2 Type 1 or Type 2, audit readiness, compliance gaps, control documentation…
fedramp
Expert guidance for FedRAMP certification and compliance. Use this skill whenever a user asks about FedRAMP authorization, ATO (Authority to Operate), cloud security for federal government, NIST SP 800-53 controls, CSP compliance, or any of the core FedRAMP document types: SSP, SAP, SAR, POA&M, CIS/CRM workbooks. Also…
gdpr-compliance
Expert GDPR compliance assistant covering all four core workflows: (1) auditing code and systems for GDPR violations, (2) drafting GDPR-compliant documents such as privacy policies, Data Processing Agreements (DPAs), and consent notices, (3) answering GDPR compliance questions with authoritative article citations, and…
pci-compliance
Expert PCI DSS compliance advisor covering PCI DSS v4.0.1 (current) and v4.0. Use this skill whenever a user asks about PCI DSS, payment card security, cardholder data protection, CDE scoping, SAQ types (A, A-EP, B, B-IP, C, C-VT, P2PE, D), ROC, AOC, QSA assessments, ASV scans, merchant levels, service provider…