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-pmbok8-earned-valuenpx skills add hoavdc/CodexKit --skill codexkit-pmbok8-earned-valuegit clone --depth 1 https://github.com/hoavdc/CodexKitWhat 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.00065 | $0.01364 |
| Opus 5 | $0.00032 | $0.00682 |
| Sonnet 5 | $0.00013 | $0.00273 |
| Haiku 4.5 | $0.00006 | $0.00136 |
Grade A, and why
codexkit-pmbok8-earned-value 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 3d ago.
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 — 144 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Earned Value Management Analyst
When to Use
- During project execution when tracking schedule and cost performance
- At monthly or sprint-end status reporting cycles
- When stakeholders need objective performance data beyond percentage-complete guesses
- When forecasting final project cost (EAC) using multiple methods
Procedure
Step 1 — Collect Baseline Data
- Confirm Budget at Completion (BAC)
- Record Planned Value (PV) at the reporting date
- Record Earned Value (EV) — value of work actually completed
- Record Actual Cost (AC) — money spent to date
Step 2 — Calculate Core Metrics
| Metric | Formula | Interpretation |
|---|---|---|
| SV | EV − PV | < 0 = behind schedule |
| CV | EV − AC | < 0 = over budget |
| SPI | EV / PV | < 1.0 = behind schedule |
| CPI | EV / AC | < 1.0 = over budget |
Step 3 — Forecast Completion
| Method | Formula | When to Use |
|---|---|---|
| EAC (typical) | BAC / CPI | Current CPI trend continues |
| EAC (atypical) | AC + (BAC − EV) | Variance was one-time |
| EAC (SPI×CPI) | AC + (BAC − EV) / (CPI × SPI) | Both schedule and cost pressure |
| ETC | EAC − AC | Remaining spend |
| TCPI (BAC) | (BAC − EV) / (BAC − AC) | Efficiency needed to hit BAC |
| TCPI (EAC) | (BAC − EV) / (EAC − AC) | Efficiency needed to hit new EAC |
| VAC | BAC − EAC | Forecast variance at completion |
Step 4 — Generate Narrative
- Summarize performance in plain language (ahead/behind, over/under)
- Apply traffic-light rating: SPI/CPI ≥ 0.95 = 🟢, 0.8–0.94 = 🟡, < 0.8 = 🔴
- Recommend corrective actions for any metric in 🟡 or 🔴 zone
- Note trends by comparing with previous period metrics
Inputs
| Input | Required | Format |
|---|---|---|
| BAC (total budget) | Yes | Currency amount |
| PV (planned value to date) | Yes | Currency amount |
| EV (earned value to date) | Yes | Currency amount |
| AC (actual cost to date) | Yes | Currency amount |
| Prior period SPI/CPI | Recommended | Decimal (for trend) |
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.
- 3d ago First seen · 144 lines · 65 tokens per session scan A 32d7620a5759
codexkit-pmbok8-earned-value is a skill published in the GitHub repository hoavdc/CodexKit (21 stars, last pushed 3mo ago), licensed MIT. It adds 65 tokens to every session and 1,364 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-08-30.
Other skills, from other repositories
data_analyst
Analyses datasets with professional rigour — statistical summaries, clear narratives, and well-chosen visualisations.
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.
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.