Fla Ascend Performance
fla-org/flash-linear-attention
Guidelines for Ascend NPU kernel / Triton-Ascend backend performance work in the FLA repo.
Hack23 Information Security Policy integration for SDLC — developer-facing mapping of ISP requirements to daily engineering activities, tooling, and evidence
Install Hack23 Information Security Policy
$ npx skills add Hack23/cia --skill hack23-information-security-policy -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Hack23/cia hack23-information-security-policy --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-information-security-policy .claude/skills/hack23-information-security-policy && 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-information-security-policy" agent skill from https://github.com/Hack23/cia/tree/master/.github/skills/hack23-information-security-policy into .claude/skills/hack23-information-security-policy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hack23-information-security-policy", 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-information-security-policyType 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-information-security-policy -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Hack23/cia hack23-information-security-policy --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-information-security-policy .agents/skills/hack23-information-security-policy && 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-information-security-policy" agent skill from https://github.com/Hack23/cia/tree/master/.github/skills/hack23-information-security-policy into .agents/skills/hack23-information-security-policy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hack23-information-security-policy", 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-information-security-policy -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Hack23/cia hack23-information-security-policy --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-information-security-policy .cursor/skills/hack23-information-security-policy && 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-information-security-policy" agent skill from https://github.com/Hack23/cia/tree/master/.github/skills/hack23-information-security-policy into .cursor/skills/hack23-information-security-policy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hack23-information-security-policy", 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-information-security-policy--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-information-security-policy -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Hack23/cia hack23-information-security-policy --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-information-security-policy .gemini/skills/hack23-information-security-policy && 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-information-security-policy" agent skill from https://github.com/Hack23/cia/tree/master/.github/skills/hack23-information-security-policy into .gemini/skills/hack23-information-security-policy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hack23-information-security-policy", 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-information-security-policyInstalls 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-information-security-policy -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-information-security-policy .github/skills/hack23-information-security-policy && 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-information-security-policy" agent skill from https://github.com/Hack23/cia/tree/master/.github/skills/hack23-information-security-policy into .github/skills/hack23-information-security-policy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hack23-information-security-policy", 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-information-security-policy -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-information-security-policy --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-information-security-policy .opencode/skills/hack23-information-security-policy && 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-information-security-policy" agent skill from https://github.com/Hack23/cia/tree/master/.github/skills/hack23-information-security-policy into .opencode/skills/hack23-information-security-policy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hack23-information-security-policy", 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-information-security-policy- GitHub stars
- 239
- Token cost
- ~3.2k tokens
- SKILL.md length
- 1,034 words
- Files
- 1
- Skills in repo
- 78
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Hack23 Information Security Policy integration for SDLC — developer-facing mapping of ISP requirements to daily engineering activities, tooling, and evidence
- Works in 7 steps: Read before act — load README,… → Classification awareness — never… → Minimal diff — surgical, auditable… → …
- Security work in your project
- SKILL.md covers Purpose, When to Use, Information Security Policy —… and Supporting Policies and When…, plus 7 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Hack23 Information Security Policy is an agent skill from Hack23/cia. Hack23 Information Security Policy integration for SDLC — developer-facing mapping of ISP requirements to daily engineering activities, tooling, and evidence
Its SKILL.md is about 3.2k 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 Security. 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
- Security work in your project
Example prompts
- “/hack23-information-security-policy”
Workflow steps
7 steps, taken from the first numbered list in SKILL.md.
- Read before act — load README, copilot-instructions, and the ISP before making changes
- Classification awareness — never escalate Public → Confidential exposure inadvertently
- Minimal diff — surgical, auditable changes; no unrelated refactors
- Evidence first — every security claim cites scanner output, ISMS control, or test
- Human-in-the-loop — Critical/High security changes require human approval before merge
- Transparent reasoning — PR descriptions link to ISP / supporting policy when relevant
- No secret handling — agents never print, commit, or send secrets; only reference names
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
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
Links to these hosts (documentation or services it may open):
github.com
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 Information Security Policy loads about 3.2k tokens when it runs. Until then it costs about 48 tokens; SKILL.md has 1,034 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). 1,034 words, ~3,228 tokens.
Download SKILL.mdSave it as
.claude/skills/hack23-information-security-policy/SKILL.md (or your agent's skills folder).- name
- hack23-information-security-policy
- description
- Hack23 Information Security Policy integration for SDLC — developer-facing mapping of ISP requirements to daily engineering activities, tooling, and evidence
- license
- Apache-2.0
Hack23 Information Security Policy Integration Skill
Purpose
Translate the Hack23 Information Security Policy — the apex document of the Hack23 ISMS — into concrete, enforceable engineering behaviour for the CIA platform. This skill connects the high-level policy (CIA triad objectives, risk appetite, roles, legal duties) to the code, workflows, reviews, and evidence that actually implement it.
Where hack23-isms-compliance describes the framework and information-security-strategy describes the strategy, this skill tells an engineer or AI agent "given the ISP and its supporting policies, what must I do in this commit, PR, or design?"
When to Use
Apply this skill when:
- ✅ Starting or reviewing any code / infrastructure / documentation change that touches data, authentication, authorization, crypto, logging, or third-party integrations
- ✅ Creating or updating a GitHub issue or PR that is security-relevant
- ✅ Onboarding a new contributor, AI agent, or repository to Hack23 standards
- ✅ Responding to a CodeQL / SonarCloud / OWASP / Dependabot finding
- ✅ Classifying data, designing an API, or integrating an external source
- ✅ Preparing release notes, SBOM, SECURITY.md, or audit evidence
- ✅ Assessing whether an AI coding agent action is policy-compliant
Do NOT use for:
- ❌ Tactical incident response (use
incident-responseskill) - ❌ Deep cryptographic implementation (use
crypto-best-practices/cryptography-policy) - ❌ Framework-level compliance mapping only (use
hack23-isms-compliance)
Information Security Policy — Core Tenets (Engineering View)
The ISP is binding on all contributors, including AI agents. Its five engineering-relevant tenets are:
| # | ISP Tenet | What it means in code/PRs | Primary Evidence |
|---|---|---|---|
| 1 | Confidentiality, Integrity, Availability (CIA triad) | Every change must preserve or strengthen C/I/A for affected assets; no change may silently lower a classification control. | THREAT_MODEL.md, SECURITY_ARCHITECTURE.md, classification labels |
| 2 | Risk-based, defence-in-depth | Controls at code, platform, CI, infra, and monitoring layers; no single point of failure. | SECURITY_ARCHITECTURE.md, Risk Register, ZAP/CodeQL scans |
| 3 | Least privilege & segregation of duties | Minimum IAM, minimum token scopes, CODEOWNERS review, permissions: block on every workflow. | .github/workflows/*, GitHub branch protection, IAM policies |
| 4 | Transparency & accountability | Signed commits, public security docs, SBOM, OpenSSF/CII badges, auditable logs. | OpenSSF Scorecard, CII badge, SECURITY.md, SBOM |
| 5 | Legal & regulatory alignment | GDPR, NIS2, EU CRA, ISO 27001:2022, NIST CSF 2.0, CIS v8. | CRA-ASSESSMENT.md, ISMS_COMPLIANCE_MAPPING.md, DPIA |
Supporting Policies and When Each Applies
The ISP is implemented through these supporting policies. An AI agent or developer MUST consult the ones that apply to the task at hand.
| Policy | Applies When | Key Engineering Checks |
|---|---|---|
| Secure Development Policy | Any code or build change | SAST+DAST+SCA pass, banned patterns, signed commits |
| Open Source Policy | Public repos, OSS dep changes, release | OpenSSF ≥7.0, CII Passing, SLSA 3, FOSSA pass, SBOM attached |
| Secrets Management Policy | Any credential, token, key, env var | No secrets in code, GitHub Secrets/SSM, rotation, scanning enabled |
| Cryptography Policy | TLS, hashing, encryption, signing | TLS 1.3, AES-256-GCM, bcrypt/argon2, RSA-4096/EC P-384, KMS-managed keys |
| Access Control Policy | AuthN/AuthZ, Spring Security, IAM | Least privilege, MFA, role separation, deny-by-default |
| Data Classification / CLASSIFICATION | New entity, API, log, export | Correct C/I/A label, handling controls per level |
| Data Protection Policy | Personal data, retention, export | GDPR lawful basis, retention, DSAR support |
| Privacy Policy | Any UI, log, analytics touching users | Minimal data, consent, cookies, opt-out paths |
| Vulnerability Management | Any finding from scanners | SLA: Crit 24h/7d, High 7d, Med 30d, Low 90d |
| Change Management | Releases, schema migrations, infra | CAB review, rollback plan, migration changeset |
| Backup & Recovery | DB or state change, DR tests | RPO/RTO respected, restore tested |
| Incident Response Plan | Suspected breach, outage, data loss | Ticket, classify, contain, notify ≤72h GDPR |
| Threat Modeling | New feature, API, trust boundary | STRIDE, attack tree, mitigation mapping |
| Third Party Management | New dependency, API, vendor, SaaS | License OK, CVE clean, data-sharing justified |
| Segregation of Duties | Workflow, deployment, review config | Author ≠ approver, CODEOWNERS enforced |
| AI Policy | Any AI / Copilot / agent action | EU AI Act risk-tier, OWASP LLM, human-in-the-loop |
| Information Security Strategy | Roadmap, architecture decisions | Aligned with CEO-approved risk appetite |
SDLC × ISP Responsibility Matrix
Each phase has mandatory ISP-derived checks. AI agents must confirm all items for their phase before proceeding.
┌────────────────┬──────────────────────────────────────────────────────────┐
│ SDLC Phase │ ISP-Derived Gate │
├────────────────┼──────────────────────────────────────────────────────────┤
│ Plan │ Classification set; threat model updated; DPIA if needed │
│ Design │ Least privilege; trust boundaries; crypto choices per │
│ │ Cryptography Policy; third-party review │
│ Implement │ Banned patterns avoided; input validation; output │
│ │ encoding; parameterized queries; no secrets │
│ Review │ CODEOWNERS; SoD (author ≠ approver); PR template met │
│ Build │ Pinned actions; reproducible; signed; SBOM generated │
│ Test │ ≥80% line / ≥70% branch; CodeQL + SCA pass; DAST │
│ │ baseline; negative test cases │
│ Release │ Signed artifacts; SLSA provenance; release notes; │
│ │ security advisories closed │
│ Operate │ Logging (no PII); alerting; rotation; DR test │
│ Respond │ Incident plan triggers; 72h GDPR notification path │
│ Retire │ Secure data deletion; key destruction; dep removal │
└────────────────┴──────────────────────────────────────────────────────────┘Show full SKILL.md (407 more words)Show less
Non-Negotiable Rules (from ISP §Acceptable Use / §Secure Engineering)
🔴 Never:
- Commit secrets, tokens, keys, or personal data — use GitHub Secrets / AWS SSM
- Disable a security control (CSRF, CSP, TLS, CodeQL) without a risk-accepted PR + CEO sign-off
- Introduce a dependency without vulnerability + license check
- Bypass CODEOWNERS, branch protection, or the signed-commit requirement
- Log request bodies, tokens, passwords, or classified data
- Ship a release with open Critical or High CVEs
- Use an unpinned GitHub Action in a workflow that has write permissions
- Process personal data without a lawful basis documented in the DPIA
🟢 Always:
- Classify new data (
Public / Internal / Confidential / Restricted) - Default to deny in authorization checks
- Parameterize all database queries
- Encode output at the rendering boundary (Vaadin
ContentMode.TEXT) - Use
@Transactionalwith explicit boundaries;readOnly = truewhere applicable - Add unit tests for the negative / unauthorized path
- Sign commits (GPG or SSH) and releases (Sigstore/cosign)
- Record security-relevant decisions in SECURITY_ARCHITECTURE.md / THREAT_MODEL.md
AI Agent & Copilot Guardrails (ISP + AI Policy)
These rules bind every AI agent (task-agent, stack-specialist, etc.) operating in this repo:
- Read before act — load README, copilot-instructions, and the ISP before making changes
- Classification awareness — never escalate Public → Confidential exposure inadvertently
- Minimal diff — surgical, auditable changes; no unrelated refactors
- Evidence first — every security claim cites scanner output, ISMS control, or test
- Human-in-the-loop — Critical/High security changes require human approval before merge
- Transparent reasoning — PR descriptions link to ISP / supporting policy when relevant
- No secret handling — agents never print, commit, or send secrets; only reference names
PR Policy Compliance Checklist
Paste into PR description for any security-relevant change:
### ISP & Supporting Policy Compliance
- [ ] Change scope and classification documented
- [ ] Threat model impact assessed (STRIDE) or confirmed N/A
- [ ] Secure Development Policy checks pass (CodeQL, SonarCloud, OWASP, SpotBugs)
- [ ] Secrets Management Policy respected (no secrets, rotation considered)
- [ ] Cryptography Policy respected (approved algorithms, key storage)
- [ ] Access Control Policy respected (least privilege, deny-by-default)
- [ ] Data Protection / Privacy Policy respected (GDPR basis, retention)
- [ ] Third Party Management respected (license, CVE, attribution)
- [ ] Open Source Policy respected (SBOM, signed release, badges)
- [ ] Logging reviewed (no PII, no secrets, useful for IR)
- [ ] Negative-path tests added
- [ ] SECURITY_ARCHITECTURE.md / THREAT_MODEL.md updated if neededEvidence & Audit Trail
Every security claim is backed by machine-verifiable evidence:
| Claim | Evidence |
|---|---|
| "Least privilege in CI" | permissions: block in workflow YAML |
| "No critical CVEs" | OWASP Dependency Check report, Dependabot status |
| "Signed releases" | Sigstore attestation, GitHub Release signatures |
| "Reproducible build" | SLSA provenance attestation |
| "Coverage ≥80%" | JaCoCo report in SonarCloud |
| "No known security hotspots" | SonarCloud Security Hotspot review |
| "License compliant" | FOSSA status badge, LICENSES/ directory |
| "SBOM complete" | CycloneDX target/bom.json attached to release |
ISMS Framework Mapping
| ISP Tenet | ISO 27001:2022 | NIST CSF 2.0 | CIS v8 |
|---|---|---|---|
| CIA Triad | A.5.1, A.8.2 | GV.RM, PR.DS | CIS 3 |
| Defence-in-depth | A.8.16, A.8.26 | PR.IP, DE.CM | CIS 4, 13 |
| Least privilege | A.5.15, A.8.2, A.8.3 | PR.AC-4 | CIS 6 |
| Transparency | A.5.31, A.5.37 | GV.OC, ID.GV | CIS 17 |
| Legal alignment | A.5.31–A.5.36 | GV.OC-03 | CIS 17.1 |
References
- Information Security Policy — apex policy
- All Hack23 ISMS Policies
- Secure Development Policy
- Open Source Policy
- Information Security Strategy
- AI Policy
- Related skills:
hack23-isms-compliance,information-security-strategy,secure-development-policy,open-source-policy,compliance-frameworks
© 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-information-security-policy of Hack23/cia.
Open the folder on GitHubat commit 6a9797b
Compare with similar skills
Hack23 Information Security Policy 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 Information Security Policy this skillHack23/cia | 239 | — | ~3.2k | Automated safety check: Pass | Apache-2.0 | |
| Fla Ascend Performancefla-org/flash-linear-attention | 5.8k | — | ~5.6k | Automated safety check: Pass | MIT | |
| Deepsec Documentation Guidevercel-labs/deepsec | 8.1k | — | ~956 | Automated safety check: Pass | Apache-2.0 | |
| Skill Scannergetsentry/skills | 1k | 4 repos | ~2.5k | Automated safety check: Warn | Apache-2.0 | |
| Serenity Aleabitoreddityan-labs/serenity-aleabitoreddit | 479 | 1 repos | ~3.3k | Automated safety check: Pass | None | |
| Security Alert Triageelastic/agent-skills | 592 | 1 repos | ~3.5k | Automated safety check: Notes | Apache-2.0 |
Similar skills
- Official
Deepsec Documentation Guide
vercel-labs/deepsec
Points the agent at deepsec's own docs to answer questions about initializing, configuring, resuming, scanning with and extending the vulnerability scanner.
- Official
Skill Scanner
getsentry/skills
Scan agent skills for security issues. An agent skill from getsentry/skills.
Serenity Aleabitoreddit
yan-labs/serenity-aleabitoreddit
Apply trader Serenity's (@aleabitoreddit) AI/semiconductor supply-chain analytical lens to US-stock ideas and market judgment.
- Official
Security Alert Triage
elastic/agent-skills
Triage Elastic Security alerts — gather context, classify threats, create cases, and acknowledge.
Shiro Attack CLI
SummerSec/ShiroAttack2
当用户要求利用、检测或测试 Apache Shiro rememberMe 反序列化漏洞 (Shiro-550, CVE-2016-4437) 时使用。触发词包括 "Shiro"、"rememberMe"、"shiro attack"、"CVE-2016-4437"、"Shiro-550"、"爆破 Shiro key"、"利用 Shiro"、"Shiro…
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 Information Security Policy
What does Hack23 Information Security Policy do?
Hack23 Information Security Policy integration for SDLC — developer-facing mapping of ISP requirements to daily engineering activities, tooling, and evidence. Hack23 Information Security Policy is an agent skill from Hack23/cia.
When should I use Hack23 Information Security Policy?
Hack23 Information Security Policy fits situations like: security work in your project.
How do I install Hack23 Information Security Policy in Claude Code?
Run `npx skills add Hack23/cia --skill hack23-information-security-policy -a claude-code`. Or copy the skill folder (.github/skills/hack23-information-security-policy in Hack23/cia) into .claude/skills/hack23-information-security-policy in your project. Claude Code loads it when a task matches its description.
How do I install Hack23 Information Security Policy in Codex?
Run `npx skills add Hack23/cia --skill hack23-information-security-policy -a codex`. Or copy the skill folder (.github/skills/hack23-information-security-policy in Hack23/cia) into .agents/skills/hack23-information-security-policy in your project. Codex loads it when a task matches its description.
Can I use Hack23 Information Security Policy 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-information-security-policy -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-information-security-policy, .gemini/skills/hack23-information-security-policy, .github/skills/hack23-information-security-policy and .opencode/skills/hack23-information-security-policy in your project.
What does Hack23 Information Security Policy need to run?
SKILL.md names no scripts, command-line tools or credentials: Hack23 Information Security Policy is instructions for the agent only.
Does Hack23 Information Security Policy access the network?
SKILL.md names 1 domain. As links in the text: github.com. This is read from the text; nothing was executed.
Is Hack23 Information Security Policy 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 Information Security Policy use?
Hack23 Information Security Policy 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 Information Security Policy use?
About 3.2k tokens (SKILL.md is roughly 13k 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 Information Security Policy?
Skills that share tags, products or a category with Hack23 Information Security Policy: Fla Ascend Performance (fla-org/flash-linear-attention, 5.8k stars), Deepsec Documentation Guide (vercel-labs/deepsec, 8.1k stars), Skill Scanner (getsentry/skills, 1k stars) and Serenity Aleabitoreddit (yan-labs/serenity-aleabitoreddit, 479 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Hack23 Information Security Policy?
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.