X Ray
pashov/skills
Generates an x-ray.md pre-audit report covering overview, enhanced threat model (protocol-type profiling, git-weighted attack surfaces, temporal risk analysis, composability dependency mapping)…
Hack23 ISMS organization-wide compliance requirements, policy enforcement, audit preparation
Install Hack23 Isms Compliance
$ npx skills add Hack23/cia --skill hack23-isms-compliance -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Hack23/cia hack23-isms-compliance --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/Hack23/cia.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.github/skills/hack23-isms-compliance .claude/skills/hack23-isms-compliance && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "hack23-isms-compliance" agent skill from https://github.com/Hack23/cia/tree/master/.github/skills/hack23-isms-compliance into .claude/skills/hack23-isms-compliance/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hack23-isms-compliance", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/Hack23/cia/tree/master/.github/skills/hack23-isms-complianceType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add Hack23/cia --skill hack23-isms-compliance -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Hack23/cia hack23-isms-compliance --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Hack23/cia.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.github/skills/hack23-isms-compliance .agents/skills/hack23-isms-compliance && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "hack23-isms-compliance" agent skill from https://github.com/Hack23/cia/tree/master/.github/skills/hack23-isms-compliance into .agents/skills/hack23-isms-compliance/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hack23-isms-compliance", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Hack23/cia --skill hack23-isms-compliance -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Hack23/cia hack23-isms-compliance --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Hack23/cia.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.github/skills/hack23-isms-compliance .cursor/skills/hack23-isms-compliance && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "hack23-isms-compliance" agent skill from https://github.com/Hack23/cia/tree/master/.github/skills/hack23-isms-compliance into .cursor/skills/hack23-isms-compliance/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hack23-isms-compliance", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/Hack23/cia.git --path .github/skills/hack23-isms-compliance--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add Hack23/cia --skill hack23-isms-compliance -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Hack23/cia hack23-isms-compliance --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Hack23/cia.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.github/skills/hack23-isms-compliance .gemini/skills/hack23-isms-compliance && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "hack23-isms-compliance" agent skill from https://github.com/Hack23/cia/tree/master/.github/skills/hack23-isms-compliance into .gemini/skills/hack23-isms-compliance/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hack23-isms-compliance", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install Hack23/cia hack23-isms-complianceInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add Hack23/cia --skill hack23-isms-compliance -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Hack23/cia.git skills-src && mkdir -p .github/skills && cp -r skills-src/.github/skills/hack23-isms-compliance .github/skills/hack23-isms-compliance && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "hack23-isms-compliance" agent skill from https://github.com/Hack23/cia/tree/master/.github/skills/hack23-isms-compliance into .github/skills/hack23-isms-compliance/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hack23-isms-compliance", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Hack23/cia --skill hack23-isms-compliance -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install Hack23/cia hack23-isms-compliance --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Hack23/cia.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.github/skills/hack23-isms-compliance .opencode/skills/hack23-isms-compliance && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "hack23-isms-compliance" agent skill from https://github.com/Hack23/cia/tree/master/.github/skills/hack23-isms-compliance into .opencode/skills/hack23-isms-compliance/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hack23-isms-compliance", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
hack23-isms-compliance- GitHub stars
- 239
- Token cost
- ~1.9k tokens
- SKILL.md length
- 608 words
- Files
- 1
- Skills in repo
- 78
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Hack23 ISMS organization-wide compliance requirements, policy enforcement, audit preparation
- Works in 4 steps: Documentation Review → Technical Controls Verification → Evidence Collection → …
- Tasks that involve Audit readiness
- SKILL.md covers Purpose, When to Use, ISMS Framework Overview and Compliance Checklist Per…, plus 7 more sections
- Calls mvn
What it does
Hack23 Isms Compliance is an agent skill from Hack23/cia. Hack23 ISMS organization-wide compliance requirements, policy enforcement, audit preparation
Its SKILL.md is about 1.9k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Legal & Compliance, covering Audit readiness and Threat modeling. The repository describes itself as: Citizen Intelligence Agency. Open-source intelligence platform analyzing Swedish political activities using AI and data visualization. Tracks politicians, government… The licence is Apache-2.0.
When your agent uses it
- Tasks that involve Audit readiness
- Tasks that involve Threat modeling
Example prompts
- “/hack23-isms-compliance”
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- Documentation Review
- Technical Controls Verification
- Evidence Collection
- Metrics Preparation
What it can do on your machine
Read from SKILL.md and the folder at commit 6a9797b. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
mvn
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Hack23 Isms Compliance loads about 1.9k tokens when it runs. Until then it costs about 29 tokens; SKILL.md has 608 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from Hack23/cia at commit 6a9797b, republished under its Apache-2.0 licence (© Hack23). 608 words, ~1,896 tokens.
Download SKILL.mdSave it as
.claude/skills/hack23-isms-compliance/SKILL.md (or your agent's skills folder).- name
- hack23-isms-compliance
- description
- Hack23 ISMS organization-wide compliance requirements, policy enforcement, audit preparation
- license
- Apache-2.0
Hack23 ISMS Compliance Skill
Purpose
Ensure all Hack23 organization projects comply with the Information Security Management System (ISMS) requirements. Covers ISO 27001:2022, NIST CSF 2.0, CIS Controls v8, NIS2, and GDPR compliance across the development lifecycle. Provides actionable guidance for audit preparation and policy enforcement.
When to Use
- ✅ Starting new projects or repositories under Hack23
- ✅ Preparing for internal or external security audits
- ✅ Reviewing compliance status of existing projects
- ✅ Implementing security controls for new features
- ✅ Creating or updating security policies and procedures
- ✅ Responding to security incidents
Do NOT use for:
- ❌ Specific code-level security patterns (use secure-code-review skill)
- ❌ Threat modeling exercises (use threat-modeling skill)
- ❌ Infrastructure security (use aws-cloudwatch-monitoring skill)
ISMS Framework Overview
┌─────────────────────────────────────────────────────────┐
│ Hack23 ISMS Framework │
├─────────────────────────────────────────────────────────┤
│ │
│ ┌──────────────┐ ┌──────────────┐ ┌──────────────┐ │
│ │ ISO 27001 │ │ NIST CSF 2.0 │ │ CIS Controls │ │
│ │ :2022 │ │ │ │ v8 │ │
│ │ 93 Controls │ │ 6 Functions │ │ 18 Controls │ │
│ └──────────────┘ └──────────────┘ └──────────────┘ │
│ │
│ ┌──────────────┐ ┌──────────────┐ ┌──────────────┐ │
│ │ NIS2 │ │ GDPR │ │ EU CRA │ │
│ │ Directive │ │ │ │ │ │
│ │ │ │ Data Privacy │ │ Cyber │ │
│ └──────────────┘ └──────────────┘ └──────────────┘ │
│ │
│ Reference: github.com/Hack23/ISMS-PUBLIC │
└─────────────────────────────────────────────────────────┘Compliance Checklist Per Repository
Mandatory Documents
| Document | Status | Description |
|---|---|---|
SECURITY.md | Required | Security policy and vulnerability reporting |
SECURITY_ARCHITECTURE.md | Required | Security architecture documentation |
THREAT_MODEL.md | Required | Threat model using STRIDE framework |
LICENSE.txt | Required | Apache 2.0 license file |
CODEOWNERS | Required | Code ownership and review requirements |
CODE_OF_CONDUCT.md | Required | Community standards |
Required GitHub Settings
- Branch protection on
main— require PR reviews - Secret scanning enabled with push protection
- Dependabot alerts enabled for all ecosystems
- Code scanning (CodeQL) enabled
- OSSF Scorecard action configured
- Signed commits required (recommended)
Required CI/CD Controls
- OWASP Dependency Check in pipeline
- SAST scanning (CodeQL or SonarCloud)
- License compliance check
- SBOM generation (CycloneDX)
- Container scanning (if applicable)
ISO 27001:2022 Control Mapping
Key Controls for Development
| Control ID | Control Name | Implementation |
|---|---|---|
| A.5.1 | Policies for information security | SECURITY.md, ISMS policies |
| A.8.4 | Access to source code | GitHub branch protection, CODEOWNERS |
| A.8.9 | Configuration management | Infrastructure as Code, version control |
| A.8.25 | Secure development lifecycle | CI/CD pipeline with security gates |
| A.8.26 | Application security requirements | Input validation, OWASP Top 10 |
| A.8.28 | Secure coding | Code review, SAST scanning |
| A.8.31 | Separation of environments | Dev/staging/prod separation |
| A.8.33 | Test information | No production data in test environments |
NIST CSF 2.0 Mapping
| Function | Category | CIA Platform Implementation |
|---|---|---|
| Identify | Asset Management | Repository inventory, SBOM |
| Protect | Access Control | Spring Security, RBAC |
| Protect | Data Security | Encryption, input validation |
| Detect | Continuous Monitoring | CodeQL, Dependabot, OSSF |
| Respond | Incident Response | SECURITY.md reporting process |
| Recover | Recovery Planning | Backup procedures, DR plans |
GDPR Compliance for Political Data
Data Classification
| Category | Examples | Handling |
|---|---|---|
| Public political data | Votes, speeches, motions | Open access, no restrictions |
| Politician profiles | Name, party, committee | Public figure exception applies |
| User accounts | Email, preferences | Minimize, encrypt, consent required |
| Analytics data | Usage patterns | Anonymize, aggregate |
Show full SKILL.md (244 more words)Show less
GDPR Requirements Checklist
- Data Processing Register maintained
- Privacy Impact Assessment for new features
- Data retention periods defined and enforced
- Right to erasure implemented for user data
- Data breach notification procedure documented
- Third-party data processor agreements in place
Audit Preparation Guide
Pre-Audit Checklist
Documentation Review
- All mandatory documents up to date
- Architecture diagrams current
- Risk register reviewed within 90 days
Technical Controls Verification
- Run full security scan suite
- Verify all CI/CD security gates active
- Check dependency vulnerability status
- Review access control configuration
Evidence Collection
bash # Generate compliance evidence mvn dependency-check:check # Vulnerability scan mvn org.cyclonedx:cyclonedx-maven-plugin:makeBom # SBOM mvn site # Project reportsMetrics Preparation
- Mean time to remediate vulnerabilities
- Code coverage percentages
- Open security issue count and age
- Dependency update compliance rate
Policy Enforcement
Automated Enforcement
# Branch protection rules (enforce via GitHub API)
protection:
required_reviews: 1
dismiss_stale_reviews: true
require_code_owner_reviews: true
required_status_checks:
- "build"
- "codeql"
- "dependency-check"
enforce_admins: trueManual Review Requirements
| Change Type | Reviewer | Approval |
|---|---|---|
| Security policy | Security lead | Required |
| Architecture change | Tech lead | Required |
| New dependency | Any reviewer | Required + security scan |
| CI/CD pipeline | DevOps + Security | Both required |
| Data model change | Tech lead | Required |
Incident Response Alignment
When a security incident occurs:
- Detect — CodeQL alerts, Dependabot alerts, manual report via
SECURITY.md - Contain — Disable affected component, revoke compromised credentials
- Eradicate — Fix vulnerability, update dependencies
- Recover — Deploy fix, verify resolution
- Lessons Learned — Update threat model, create ADR if architectural change needed
ISMS Reference
The authoritative ISMS documentation is maintained at:
- Repository:
github.com/Hack23/ISMS-PUBLIC - Secure Development Policy:
Secure_Development_Policy.md - Key Management Policy:
Key_Management_Policy.md - Access Control Policy:
Access_Control_Policy.md
All Hack23 projects must align with these organization-wide policies.
© Hack23, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .github/skills/hack23-isms-compliance of Hack23/cia.
Open the folder on GitHubat commit 6a9797b
Compare with similar skills
Hack23 Isms Compliance next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Hack23 Isms Compliance this skillHack23/cia | 239 | — | ~1.9k | Automated safety check: Pass | Apache-2.0 | |
| X Raypashov/skills | 1.2k | 1 repos | ~10k | Automated safety check: Pass | MIT | |
| Xray Pre Auditccashwell/evm-cortex | 131 | — | ~25k | Automated safety check: Pass | MIT | |
| Hardening Windows Endpoint With Cis Benchmarkmukul975/Anthropic-Cybersecurity-Skills | 34k | — | ~2.2k | Automated safety check: Pass | Apache-2.0 | |
| Hardening Linux Endpoint With Cis Benchmarkmukul975/Anthropic-Cybersecurity-Skills | 34k | — | ~1.8k | Automated safety check: Notes | Apache-2.0 | |
| PCI DSS Compliancewshobson/agents | 40k | 10 repos | ~1.9k | Automated safety check: Pass | MIT |
Similar skills
Xray Pre Audit
ccashwell/evm-cortex
A skill your agent uses when preparing for a security audit, performing reconnaissance on a new codebase, or creating a protocol overview.
Hardening Windows Endpoint With Cis Benchmark
mukul975/Anthropic-Cybersecurity-Skills
Hardens Windows endpoints using CIS (Center for Internet Security) Benchmark recommendations to reduce attack surface, enforce security baselines, and meet compliance requirements.
Hardening Linux Endpoint With Cis Benchmark
mukul975/Anthropic-Cybersecurity-Skills
Hardens Linux endpoints using CIS Benchmark recommendations for Ubuntu, RHEL, and CentOS to reduce attack surface, enforce security baselines, and meet compliance requirements.
PCI DSS Compliance
wshobson/agents
Reference for building payment systems that meet PCI DSS: the 12 requirements, merchant levels, data that must never be stored, tokenization and encryption.
Security Compliance
sangrokjung/claude-forge
Guides security professionals in implementing defense-in-depth security architectures, achieving compliance with industry frameworks (SOC2, ISO27001, GDPR, HIPAA), conducting threat modeling and…
More from Hack23/cia
All 78 skills in this repoAccessibility Wcag Patterns
Hack23/cia
WCAG 2.1 AA compliance, ARIA attributes, keyboard navigation, screen reader optimization for accessible political data platforms
Advanced Data Visualization
Hack23/cia
Advanced chart types, D3.js/Vaadin Charts patterns, political data visualization, time series analysis
AI Governance
Hack23/cia
AI governance, EU AI Act compliance, OWASP LLM security, responsible AI practices for GitHub Copilot agents
API Integration
Hack23/cia
External API integration patterns, retry logic, circuit breakers, caching, rate limiting for government data APIs
AWS Cloudwatch Monitoring
Hack23/cia
AWS CloudWatch metrics, alarms, dashboards, log insights, and application monitoring for the CIA platform
AWS Security Architecture
Hack23/cia
AWS security best practices, VPC security, IAM, KMS, CloudTrail, GuardDuty for CIA platform deployment
Related
Categories
Questions about Hack23 Isms Compliance
What does Hack23 Isms Compliance do?
Hack23 ISMS organization-wide compliance requirements, policy enforcement, audit preparation. Hack23 Isms Compliance is an agent skill from Hack23/cia.
When should I use Hack23 Isms Compliance?
Hack23 Isms Compliance fits situations like: tasks that involve Audit readiness; tasks that involve Threat modeling.
How do I install Hack23 Isms Compliance in Claude Code?
Run `npx skills add Hack23/cia --skill hack23-isms-compliance -a claude-code`. Or copy the skill folder (.github/skills/hack23-isms-compliance in Hack23/cia) into .claude/skills/hack23-isms-compliance in your project. Claude Code loads it when a task matches its description.
How do I install Hack23 Isms Compliance in Codex?
Run `npx skills add Hack23/cia --skill hack23-isms-compliance -a codex`. Or copy the skill folder (.github/skills/hack23-isms-compliance in Hack23/cia) into .agents/skills/hack23-isms-compliance in your project. Codex loads it when a task matches its description.
Can I use Hack23 Isms Compliance in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Hack23/cia --skill hack23-isms-compliance -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/hack23-isms-compliance, .gemini/skills/hack23-isms-compliance, .github/skills/hack23-isms-compliance and .opencode/skills/hack23-isms-compliance in your project.
What does Hack23 Isms Compliance need to run?
Going by SKILL.md and its folder, Hack23 Isms Compliance needs the command-line tools its instructions call (mvn).
Does Hack23 Isms Compliance access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Hack23 Isms Compliance safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Hack23 Isms Compliance use?
Hack23 Isms Compliance is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Hack23 Isms Compliance use?
About 1.9k tokens (SKILL.md is roughly 7.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Hack23 Isms Compliance?
Skills that share tags, products or a category with Hack23 Isms Compliance: X Ray (pashov/skills, 1.2k stars), Xray Pre Audit (ccashwell/evm-cortex, 131 stars), Hardening Windows Endpoint With Cis Benchmark (mukul975/Anthropic-Cybersecurity-Skills, 34k stars) and Hardening Linux Endpoint With Cis Benchmark (mukul975/Anthropic-Cybersecurity-Skills, 34k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Hack23 Isms Compliance?
Hack23 (a GitHub organization) maintains it in Hack23/cia, which has 239 GitHub stars. The repository holds 78 skills in this directory. The repository was last updated on October 6, 2026.
Source: Hack23/cia on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.