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-okr-writernpx skills add hoavdc/CodexKit --skill codexkit-okr-writergit 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.00073 | $0.01004 |
| Opus 5 | $0.00036 | $0.00502 |
| Sonnet 5 | $0.00015 | $0.00201 |
| Haiku 4.5 | $0.00007 | $0.00100 |
Grade A, and why
codexkit-okr-writer 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 2d 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 — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OKR Writer
Purpose
Create well-structured OKRs that connect strategic ambition to measurable outcomes, with proper cascade from company level down to team or project level.
When to use
- quarterly or annual OKR setting cycles
- aligning a new project to company strategy
- when OKRs are vague, activity-based, or poorly measurable
- creating a check-in cadence for tracking OKR progress
When not to use
- KPI dashboards or operational metrics tracking
- individual performance reviews or compensation decisions
- daily or weekly task management
Inputs
- organizational level (company / department / team / project)
- strategic context or parent OKR to cascade from
- time horizon (quarter, half-year, or annual)
- current baseline metrics for proposed key results
- known constraints or dependencies
Procedure
- Draft Objective — must be:
- Inspiring and qualitative (no numbers in the objective)
- Achievable within the time horizon
- Within the team's sphere of influence
- Example: "Become the most trusted partner for enterprise clients"
- Write 3–5 Key Results per Objective — each must be:
- Measurable with a specific number
- Outcome-based, not activity-based
- Ambitious: 70% achievement = success
- Template: "Increase/Reduce [metric] from [baseline] to [target] by [date]"
- Validate quality — reject common anti-patterns:
- ❌ Activity KR: "Launch 3 features" → ✅ Outcome KR: "Increase feature adoption to 40%"
- ❌ Binary KR: "Complete migration" → ✅ Measurable KR: "Migrate 95% of accounts by Q2"
- Cascade alignment — map each team OKR to its parent department/company OKR.
- Create check-in template for weekly or bi-weekly tracking:
- Confidence score (0–10, where 7 = on track)
- Current value vs target
- Blockers and help needed
- Set scoring method — at quarter-end:
- 0.0–0.3: Failed to make progress
- 0.4–0.6: Made progress but fell short
- 0.7–1.0: Delivered (0.7 is the sweet spot for stretch OKRs)
What ships with it
4 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.
- 2d ago First seen · 107 lines · 73 tokens per session scan A 6f605edfc508
codexkit-okr-writer is a skill published in the GitHub repository hoavdc/CodexKit (21 stars, last pushed 3mo ago), licensed MIT. It adds 73 tokens to every session and 1,004 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-08-30.
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.
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.
analyzing-changes
Analyzes code changes, detects documentation drift, and evaluates change impact scope. Use when reviewing diffs, checking doc sync, or running pre-commit analysis. Automatically triggered after design-level changes or refactoring.