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-ops-kpi-packagernpx skills add hoavdc/CodexKit --skill codexkit-ops-kpi-packagergit 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.00056 | $0.00569 |
| Opus 5 | $0.00028 | $0.00284 |
| Sonnet 5 | $0.00011 | $0.00114 |
| Haiku 4.5 | $0.00006 | $0.00057 |
Grade A, and why
codexkit-ops-kpi-packager 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 — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ops KPI Packager
Purpose
Turn raw metrics and exception notes into a compact control view.
When to use
- metrics are reported regularly but still need manual cleanup
- operations reviews need one concise input file
- teams are spending time formatting instead of acting
When not to use
- the user needs deep analysis or improvement design
- there is no reliable source data for the KPI snapshot
Inputs
- metrics and targets
- exceptions or service failures
- owner notes or corrective actions
Procedure
- Normalize the metrics into current, target, and trend.
- Flag only the exceptions that materially need attention.
- Pair each exception with owner and next action if known.
- Separate observations from assumptions.
- End with a short review-ready summary.
Output
- KPI snapshot
- exception list
- owner follow-ups
- short summary for the next ops review
Definition of done
- the review can focus on action, not formatting
- metric misses and owner actions are easy to scan
- noise is reduced without hiding material exceptions
Examples
- "Package these warehouse KPIs into a weekly control view."
- "Turn this ops scorecard and issue log into one review-ready update."
Quality Criteria
- Data sources and assumptions are explicitly stated
- Calculations are reproducible from provided inputs
- Visualizations or tables have clear labels, units, and time ranges
- Caveats and confidence levels are documented for estimates
Verification (4C)
| Check | Question |
|---|---|
| Correctness | Are formulas, aggregations, and statistical methods applied correctly? |
| Completeness | Does the analysis cover all requested metrics and time ranges? |
| Context-fit | Are the chosen metrics relevant to the business question being answered? |
| Consequence | If this data were used for a decision today, what blind spots remain? |
Edge Cases
- Missing or incomplete data — Document gaps and their potential impact on conclusions. Provide ranges instead of point estimates.
- Outliers skewing results — Report with and without outliers. Document the decision to include or exclude.
- Changing data definitions mid-period — Split analysis at the change boundary and note the schema difference.
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.
- 2d ago First seen · 82 lines · 56 tokens per session scan A b771d53e2635
codexkit-ops-kpi-packager is a skill published in the GitHub repository hoavdc/CodexKit (21 stars, last pushed 3mo ago), licensed MIT. It adds 56 tokens to every session and 569 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
agent-project-board-sync
Agent skill for project-board-sync - invoke with $agent-project-board-sync.
agent-issue-tracker
Agent skill for issue-tracker - invoke with $agent-issue-tracker.
agent-planner
Agent skill for planner - invoke with $agent-planner.
add-linear
Add Linear channel integration via Chat SDK. Issue comment threads as conversations.
maintain
Maintain the slopus/happy open source project. Triage issues, draft closing comments, find duplicates, check if bugs are fixed on main, and engage with community contributors. NEVER posts comments or closes issues without showing exact text and getting approval first.
apm-triage-panel
Use this skill to triage one microsoft/apm issue selected by the daily sweep, the status/needs-triage fast path, or manual dispatch. Emit one synthesized comment with a decision, label set, exact milestone, and suggested next action.