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 agentmods add skills/hoavdc/codexkit/codexkit-risk-registernpx skills add hoavdc/CodexKit --skill codexkit-risk-registergit clone --depth 1 https://github.com/hoavdc/CodexKitWrote 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/hoavdc/codexkit/codexkit-risk-register)<a href="https://agentmods.dev/skills/hoavdc/codexkit/codexkit-risk-register"><img src="https://agentmods.dev/badge/skills/hoavdc/codexkit/codexkit-risk-register.svg" alt="Measured on agentmods" 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 | $0.00063 | $0.00985 |
| Opus 5 | $0.00032 | $0.00492 |
| Sonnet 5 | $0.00013 | $0.00197 |
| Haiku 4.5 | $0.00006 | $0.00098 |
Grade A, and why
codexkit-risk-register 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 yesterday.
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 — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Risk Register Manager
Purpose
Systematically identify, assess, and manage project risks using a structured register with probability/impact scoring and defined response strategies.
When to use
- project kick-off to establish the initial risk baseline
- sprint or milestone reviews to update and add emerging risks
- before major decisions to assess risk exposure
- when stakeholders request a risk assessment report
When not to use
- live incident response or post-mortem analysis
- security vulnerability scanning (use security tools)
- personal task risk assessment
Inputs
- project scope, objectives, and constraints
- project type (predictive / adaptive / hybrid)
- stakeholder list and their risk tolerance
- known assumptions and dependencies
- lessons learned from similar projects (if available)
Procedure
- Identify risks using multiple sources:
- Internal: technical complexity, resource gaps, schedule pressure, budget
- External: market shifts, regulatory changes, vendor reliability, geopolitical
- PMBOK 8 emphasis: sustainability risks (ESG, climate, social impact)
- Techniques: brainstorming, PESTLE analysis, Risk Breakdown Structure (RBS)
- Assess each risk qualitatively:
- Probability: Very Low (0.1) / Low (0.3) / Medium (0.5) / High (0.7) / Very High (0.9)
- Impact: Very Low (0.05) / Low (0.1) / Medium (0.2) / High (0.4) / Very High (0.8)
- Risk Score = Probability × Impact
- Red zone (≥ 0.25): immediate response required
- Yellow zone: response plan needed
- Green zone: monitor only
- Define response strategy:
- For threats: Avoid / Transfer / Mitigate / Accept (active or passive)
- For opportunities: Exploit / Share / Enhance / Accept
- Assign ownership — every risk has one named owner.
- Track residual risk — after response, re-score to verify reduction.
- SAFe integration — for SAFe teams, use ROAM board:
- R = Resolved | O = Owned | A = Accepted | M = Mitigated
What ships with it
1 file 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.
- yesterday First seen · 103 lines · 63 tokens per session scan A 55eff3ca4835
codexkit-risk-register is a skill published in the GitHub repository hoavdc/CodexKit (21 stars, last pushed 3mo ago), licensed MIT. It adds 63 tokens to every session and 985 once invoked, about $0.0003 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-09-03.
Other skills, from other repositories
reducing-aigc-detection
Systematically reduce AIGC detection rates in academic papers (Chinese/English). Analyzes detection reports, identifies high-impact sections, applies multi-layer rewriting strategies preserving formatting/footnotes, and verifies results. Supports 维普/知网/Turnitin platforms.
architecting-security
安全架构与治理：威胁建模 (STRIDE/PASTA/LINDDUN)、零信任身份架构、IAM/SSO/MFA/PAM、合规框架 (SOC2/PCI/HIPAA/GDPR)、DLP、隐私工程、安全控制设计。Use when designing security architecture, threat modeling new systems, implementing zero-trust identity, designing IAM/SSO/PAM, building compliance evidence chains, or planning privacy-by-design.
cultivating-personas
Distills AI agent voice patterns from conversation into a Persona Voice Card v1.0 (self/user/language/register/emojipolicy/flourish only — no judgment-shaped fields), validates schema + content safety + differentiation, and routes contributions through the existing submission portal. Use when the user wants to…
defending-applications
Application security defense knowledge for builders. Covers Web/API/GraphQL hardening (XSS/SQLi/SSRF/IDOR/BOLA/Mass Assignment/deserialization/upload/path traversal), authentication/authorization (OAuth 2.0/OIDC/JWT/Session/Cookie/SAML/SSO), and LLM application security (prompt injection, jailbreak, RAG poisoning…
detecting-and-responding
蓝队与紫队工程：检测规则编写、SIEM/EDR 调优、事件响应、数字取证、威胁狩猎、ATT&CK 映射、紫队演练闭环。Use when writing Sigma/YARA detection rules, tuning SIEM noise, responding to security incidents, conducting forensic analysis, hunting threats, or running purple team exercises.
securing-cloud-and-supply-chain
云原生与软件供应链安全防御。容器/K8s 加固、Service Mesh、CI/CD 安全、SLSA/SBOM/Sigstore、云 IAM、Secrets 管理、IaC 安全。Use when hardening Kubernetes clusters, auditing CI/CD pipelines, implementing supply chain security, managing cloud IAM, or reviewing IaC code.