Trust Center Builder
GRCEngClub/claude-grc-engineering
Builds and deploys a serverless trust center that publishes a company's compliance posture, with gated access to audit reports and an admin dashboard.
Secure change control: RFC process, testing requirements, rollback procedures per ISO 27001 A.8.9, A.8.32
$ npx skills add Hack23/cia --skill change-management -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Hack23/cia change-management --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/change-management .claude/skills/change-management && 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 "change-management" agent skill from https://github.com/Hack23/cia/tree/master/.github/skills/change-management into .claude/skills/change-management/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "change-management", 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/change-managementType 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 change-management -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Hack23/cia change-management --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/change-management .agents/skills/change-management && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "change-management" agent skill from https://github.com/Hack23/cia/tree/master/.github/skills/change-management into .agents/skills/change-management/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "change-management", 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 change-management -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Hack23/cia change-management --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/change-management .cursor/skills/change-management && 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 "change-management" agent skill from https://github.com/Hack23/cia/tree/master/.github/skills/change-management into .cursor/skills/change-management/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "change-management", 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/change-management--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 change-management -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Hack23/cia change-management --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/change-management .gemini/skills/change-management && 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 "change-management" agent skill from https://github.com/Hack23/cia/tree/master/.github/skills/change-management into .gemini/skills/change-management/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "change-management", 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 change-managementInstalls 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 change-management -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/change-management .github/skills/change-management && 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 "change-management" agent skill from https://github.com/Hack23/cia/tree/master/.github/skills/change-management into .github/skills/change-management/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "change-management", 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 change-management -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 change-management --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/change-management .opencode/skills/change-management && 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 "change-management" agent skill from https://github.com/Hack23/cia/tree/master/.github/skills/change-management into .opencode/skills/change-management/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "change-management", 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.
change-managementSecure change control: RFC process, testing requirements, rollback procedures per ISO 27001 A.8.9, A.8.32
Change Management is an agent skill from Hack23/cia. Secure change control: RFC process, testing requirements, rollback procedures per ISO 27001 A.8.9, A.8.32
Its SKILL.md is about 3k 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 SOC 2 and security compliance. 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.
Read from SKILL.md and the folder at commit 6a9797b. It shows what the files ask for, not the result of running them.
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.
Shell commands in SKILL.md call:
psqlpg_dumpcurlFrom the folder's file list and the shell code blocks in SKILL.md.
Links to these hosts (documentation or services it may open):
github.comFrom URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Change Management loads about 3k tokens when it runs. Until then it costs about 31 tokens; SKILL.md has 695 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.
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.
The full file from Hack23/cia at commit 6a9797b, republished under its Apache-2.0 licence (© Hack23). 695 words, ~3,041 tokens.
.claude/skills/change-management/SKILL.md (or your agent's skills folder).This skill provides systematic guidance for implementing secure change control within the CIA platform, ensuring all changes are documented, tested, approved, and reversible per ISO 27001 A.8.9 (Configuration Management) and A.8.32 (Change Management).
Apply this skill when:
Do NOT skip for:
Definition: Low-risk, routine changes with documented procedures and automated security validation.
Examples:
Requirements:
GitHub Actions Workflow:
name: Standard Change Validation
# Pinned: actions/checkout@b4ffde65f46336ab88eb53be808477a3936bae11 # v4.1.1
on:
pull_request:
paths:
- '**.md'
- 'docs/**'
- 'test/**'
jobs:
validate-standard-change:
runs-on: ubuntu-latest
steps:
- name: Checkout code
uses: actions/checkout@b4ffde65f46336ab88eb53be808477a3936bae11 # v4.1.1
- name: Validate documentation
run: |
echo "Validating standard change..."
# Markdown linting
npx markdownlint-cli2 "**/*.md"
- name: Check for security issues
run: |
# Ensure no secrets in documentation
if grep -r "password\|secret\|key" --include="*.md" .; then
echo "ERROR: Potential secrets in documentation"
exit 1
fi
- name: Auto-approve standard change
if: success()
run: echo "Standard change pre-approved - deploy authorized"Definition: Medium-risk changes requiring CEO review and explicit approval before implementation.
Examples:
.github/agents/*.md, .github/copilot-mcp*.json)Requirements:
Request for Change (RFC) Template:
# RFC: [Change Title]
## Change Information
- **RFC ID**: RFC-2025-001
- **Requester**: Developer Name
- **Date**: 2025-02-10
- **Priority**: Normal
- **Category**: Infrastructure
## Business Justification
Why is this change needed? What business problem does it solve?
## Technical Description
Detailed technical description of the change.
## Risk Assessment
| Risk Category | Level | Mitigation |
|---------------|-------|------------|
| Security | Medium | Security review completed |
| Availability | Low | Blue-green deployment |
| Data Integrity | Low | Database backup before migration |
## Testing Plan
- [ ] Unit tests pass (80% coverage minimum)
- [ ] Integration tests pass
- [ ] Security scanning clean (CodeQL, OWASP)
- [ ] Performance testing completed
- [ ] Staging environment validation
## Rollback Procedure
1. Identify rollback trigger conditions
2. Steps to revert change
3. Data recovery procedures (if applicable)
4. Estimated rollback time: 15 minutes
## Implementation Schedule
- **Planned Start**: 2025-02-15 10:00 UTC
- **Estimated Duration**: 2 hours
- **Planned Completion**: 2025-02-15 12:00 UTC
## Approval
- [ ] CEO Review
- [ ] CEO Approval
- [ ] Deployment Authorization
**CEO Signature**: ________________ **Date**: __________Definition: Critical changes required to restore service availability or address active security incidents.
Triggers:
Authorization:
Emergency Change Workflow:
sequenceDiagram
participant Inc as 🚨 Incident
participant CEO as 👨💼 CEO
participant Impl as 🔧 Implementation
participant Monitor as 📊 Monitoring
participant Review as 📋 Post-Review
Inc->>CEO: 1. Incident Detected
CEO->>CEO: 2. Assess Severity
CEO->>CEO: 3. Authorize Emergency Change
CEO->>Impl: 4. Implement Fix
Impl->>Monitor: 5. Verify Fix Applied
Monitor->>CEO: 6. Confirm Resolution
CEO->>CEO: 7. Document Change (4h deadline)
CEO->>Review: 8. Schedule Post-Review (24h)
Review->>Review: 9. Lessons LearnedgitGraph
commit id: "main"
branch feature/new-analysis-tool
checkout feature/new-analysis-tool
commit id: "Implement analysis logic"
commit id: "Add unit tests"
commit id: "Update documentation"
checkout main
merge feature/new-analysis-tool tag: "PR #123 - CEO Approved"
commit id: "Deploy to production"# .github/branch-protection-config.yml
# Branch protection for main branch
branch-protection:
main:
required_status_checks:
strict: true
contexts:
- "build"
- "test"
- "security-scan"
- "codeql-analysis"
required_pull_request_reviews:
required_approving_review_count: 1
dismiss_stale_reviews: true
require_code_owner_reviews: true
require_last_push_approval: true
restrictions:
users:
- "pethers" # CEO - only authorized deployer
teams: []
enforce_admins: true
require_linear_history: true
allow_force_pushes: false
allow_deletions: false#!/bin/bash
# Database schema rollback script
set -euo pipefail
BACKUP_DATE=${1:-$(date +%Y%m%d)}
BACKUP_FILE="/backups/database-${BACKUP_DATE}.sql"
rollback_database() {
echo "🔄 Starting database rollback..."
# 1. Create pre-rollback backup
echo "📦 Creating pre-rollback backup..."
pg_dump -h $DB_HOST -U $DB_USER -d cia_database > "/backups/pre-rollback-$(date +%Y%m%d-%H%M%S).sql"
# 2. Stop application services
echo "🛑 Stopping application services..."
systemctl stop cia-application
# 3. Restore from backup
echo "📥 Restoring database from backup..."
psql -h $DB_HOST -U $DB_USER -d cia_database < "${BACKUP_FILE}"
# 4. Verify restoration
echo "✅ Verifying database restoration..."
psql -h $DB_HOST -U $DB_USER -d cia_database -c "\
SELECT COUNT(*) as table_count FROM information_schema.tables \
WHERE table_schema = 'public';"
# 5. Restart application
echo "🚀 Restarting application services..."
systemctl start cia-application
# 6. Verify application health
echo "🏥 Checking application health..."
curl -f http://localhost:8080/actuator/health || {
echo "❌ Application health check failed"
exit 1
}
echo "✅ Database rollback completed successfully"
}
# Execute rollback
rollback_database| Metric | Target | Measurement | Review Frequency |
|---|---|---|---|
| Change Success Rate | >95% | Deployments without rollback | Weekly |
| Mean Time to Deploy | <2 hours | From approval to production | Monthly |
| Rollback Rate | <5% | Changes requiring rollback | Monthly |
| Emergency Change Rate | <2% | Emergency vs total changes | Monthly |
| Change Lead Time | <7 days | RFC to deployment | Quarterly |
| Security Gate Pass Rate | 100% | First-time security scan pass | Weekly |
Control Objective: Configuration of systems and networks documented and controlled.
Implementation:
Control Objective: Changes to information processing facilities and systems controlled.
Implementation:
PR.IP-3: Configuration change control processes in place
PR.IP-4: Backups of information conducted, maintained, tested
CIS Control 3.14: Log Configuration Changes
CIS Control 4.1: Establish and Maintain Secure Configuration Process
© Hack23, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. 1 hidden character (zero-width or bidirectional) removed. Raw file
Just SKILL.md in .github/skills/change-management of Hack23/cia.
Open the folder on GitHubat commit 6a9797b
Change Management 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 |
|---|---|---|---|---|---|---|
| Change Management this skillHack23/cia | 239 | — | ~3k | Automated safety check: Pass | Apache-2.0 | |
| Trust Center BuilderGRCEngClub/claude-grc-engineering | 419 | — | ~2.6k | Automated safety check: Pass | Custom licence | |
| Policy OpaAgentSecOps/SecOpsAgentKit | 219 | 1 repos | ~3.5k | Automated safety check: Pass | Custom licence | |
| AWS Inspector ExpertGRCEngClub/claude-grc-engineering | 419 | — | ~1.4k | Automated safety check: Pass | Custom licence | |
| Nist 800 53Sushegaad/Claude-Skills-Governance-Risk-and-Compliance | 939 | 1 repos | ~3.3k | Automated safety check: Pass | MIT | |
| Soc2Sushegaad/Claude-Skills-Governance-Risk-and-Compliance | 939 | 1 repos | ~2.7k | Automated safety check: Pass | MIT |
GRCEngClub/claude-grc-engineering
Builds and deploys a serverless trust center that publishes a company's compliance posture, with gated access to audit reports and an admin dashboard.
AgentSecOps/SecOpsAgentKit
Policy-as-code enforcement and compliance validation using Open Policy Agent (OPA).
GRCEngClub/claude-grc-engineering
Expertise in evaluating AWS accounts for compliance — what checks are meaningful, which SCF controls they map to, and how to interpret aws CLI output.
Sushegaad/Claude-Skills-Governance-Risk-and-Compliance
NIST SP 800-53 Rev 5 compliance advisor — all 20 control families (AC, AT, AU, CA, CM, CP, IA, IR, MA, MP, PE, PL, PM, PS, PT, RA, SA, SC, SI, SR), Low/Moderate/High baseline selection, FIPS 199/200…
Sushegaad/Claude-Skills-Governance-Risk-and-Compliance
Expert SOC 2 compliance assistant covering all five Trust Services Criteria (Security/CC, Availability/A, Confidentiality/C, Processing Integrity/PI, Privacy/P).
mlunato47/claude-grc-plugin
Senior GRC analyst expertise across 18 compliance frameworks — NIST 800-53, FedRAMP (Rev5 + 20x/CR26, KSIs, VDR/VER, Certification Classes A–D), DoD/DoW Impact Levels (IL2–IL6, DISA Cloud SRG), ITAR…
Hack23/cia
WCAG 2.1 AA compliance, ARIA attributes, keyboard navigation, screen reader optimization for accessible political data platforms
Hack23/cia
Advanced chart types, D3.js/Vaadin Charts patterns, political data visualization, time series analysis
Hack23/cia
AI governance, EU AI Act compliance, OWASP LLM security, responsible AI practices for GitHub Copilot agents
Hack23/cia
External API integration patterns, retry logic, circuit breakers, caching, rate limiting for government data APIs
Hack23/cia
AWS CloudWatch metrics, alarms, dashboards, log insights, and application monitoring for the CIA platform
Hack23/cia
AWS security best practices, VPC security, IAM, KMS, CloudTrail, GuardDuty for CIA platform deployment
Secure change control: RFC process, testing requirements, rollback procedures per ISO 27001 A.8.9, A.8.32. Change Management is an agent skill from Hack23/cia.
Change Management fits situations like: tasks that involve SOC 2 and security compliance.
Run `npx skills add Hack23/cia --skill change-management -a claude-code`. Or copy the skill folder (.github/skills/change-management in Hack23/cia) into .claude/skills/change-management in your project. Claude Code loads it when a task matches its description.
Run `npx skills add Hack23/cia --skill change-management -a codex`. Or copy the skill folder (.github/skills/change-management in Hack23/cia) into .agents/skills/change-management in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Hack23/cia --skill change-management -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/change-management, .gemini/skills/change-management, .github/skills/change-management and .opencode/skills/change-management in your project.
Going by SKILL.md and its folder, Change Management needs the command-line tools its instructions call (psql, pg_dump and curl). Our summary lists: Node.js.
SKILL.md names 1 domain. As links in the text: github.com. This is read from the text; nothing was executed.
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.
Change Management 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.
About 3k tokens (SKILL.md is roughly 12k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Change Management: Trust Center Builder (GRCEngClub/claude-grc-engineering, 419 stars), Policy Opa (AgentSecOps/SecOpsAgentKit, 219 stars), AWS Inspector Expert (GRCEngClub/claude-grc-engineering, 419 stars) and Nist 800 53 (Sushegaad/Claude-Skills-Governance-Risk-and-Compliance, 939 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
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.