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-project-governance-pilotnpx skills add hoavdc/CodexKit --skill codexkit-project-governance-pilotgit 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-project-governance-pilot)<a href="https://agentmods.dev/skills/hoavdc/codexkit/codexkit-project-governance-pilot"><img src="https://agentmods.dev/badge/skills/hoavdc/codexkit/codexkit-project-governance-pilot.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.00088 | $0.00764 |
| Opus 5 | $0.00044 | $0.00382 |
| Sonnet 5 | $0.00018 | $0.00153 |
| Haiku 4.5 | $0.00009 | $0.00076 |
Grade A, and why
codexkit-project-governance-pilot 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 — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Governance Pilot
Purpose
Build a practical governance pack that helps a project deliver value, make decisions fast, and surface risk early.
When to use
- A new initiative needs a charter and operating model.
- A multi-team program has unclear ownership or cadence.
- A troubled project needs a governance reset before more execution.
When not to use
- A team only needs a sprint backlog or daily standup summary.
- The request is just a status rewrite with no governance decision.
Inputs
- project purpose, expected outcomes, and success measures
- timeline, milestones, budget, and constraints
- stakeholder list, sponsor, and delivery teams
- current delivery model or likely model: predictive, adaptive, hybrid
- known risks, dependencies, or escalation pain points
Procedure
- Frame the value case in business terms, not task terms.
- Choose the working model: predictive, adaptive, hybrid, Scrum, or SAFe-heavy.
- Define decision rights with a simple RACI and escalation path.
- Map stakeholders by influence, dependency, and communication need.
- Set the operating cadence: steering review, delivery review, RAID review, and executive update rhythm.
- Define the core artifacts: charter, RAID structure, dependency view, scorecard, and status format.
- Mark assumptions, missing inputs, and the first 30-day setup actions.
Output
- project value statement and success definition
- governance model with roles and decision rights
- stakeholder and communication matrix
- cadence calendar and meeting purposes
- RAID and dependency structure
- first-action list with owners
Definition of done
- A sponsor can see how decisions get made.
- Teams know which cadence and artifacts they must maintain.
- Risks, dependencies, and escalation triggers are explicit.
- Success is framed around value delivery, not just activity completion.
Examples
- "Set up governance for a cross-functional transformation project with product, finance, and operations teams."
- "Our program is slipping because nobody owns decisions. Build a governance reset pack we can use this week."
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.
- yesterday First seen · 89 lines · 88 tokens per session scan A e4eccdb15bf5
codexkit-project-governance-pilot is a skill published in the GitHub repository hoavdc/CodexKit (21 stars, last pushed 3mo ago), licensed MIT. It adds 88 tokens to every session and 764 once invoked, about $0.0004 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.