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/yonatangross/orchestkit/analyticsnpx skills add yonatangross/orchestkit --skill analyticsgit clone --depth 1 https://github.com/yonatangross/orchestkitWrote 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/yonatangross/orchestkit/analytics)<a href="https://agentmods.dev/skills/yonatangross/orchestkit/analytics"><img src="https://agentmods.dev/badge/skills/yonatangross/orchestkit/analytics.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.00062 | $0.02951 |
| Opus 5 | $0.00031 | $0.01476 |
| Sonnet 5 | $0.00012 | $0.00590 |
| Haiku 4.5 | $0.00006 | $0.00295 |
Grade A, and why
analytics 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 today.
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.
Cross-Project Analytics
Query local analytics data from ~/.claude/analytics/. All data is local-only, privacy-safe (hashed project IDs, no PII).
Answer usage questions from the local files, never from guesswork: agent usage (which agents and how often — not which model, see the caveats) lives in ~/.claude/analytics/agent-usage.jsonl; hook performance and failures live in ~/.claude/analytics/hook-timing.jsonl; token and cost totals live in ~/.claude/stats-cache.json. Query them with jq one-liners (below) and present real counts, not pointers to dashboards.
Subcommands
Parse the user's argument to determine which report to show. If no argument provided, use AskUserQuestion to let them pick.
| Subcommand | Description | Data Source | Reference |
|---|---|---|---|
agents |
Top agents by frequency and success rate (duration/model unavailable — #3034) | agent-usage.jsonl |
${CLAUDE_PLUGIN_ROOT}/skills/analytics/references/jq-queries.md |
models |
Model delegation from token totals in stats-cache.json. Per-spawn attribution is unavailable (#3034) |
stats-cache.json |
${CLAUDE_PLUGIN_ROOT}/skills/analytics/references/jq-queries.md |
skills |
Top skills by invocation count | skill-usage.jsonl |
${CLAUDE_PLUGIN_ROOT}/skills/analytics/references/jq-queries.md |
hooks |
Slowest hooks and failure rates | hook-timing.jsonl |
${CLAUDE_PLUGIN_ROOT}/skills/analytics/references/jq-queries.md |
teams |
Team spawn counts, idle time, task completions | team-activity.jsonl |
${CLAUDE_PLUGIN_ROOT}/skills/analytics/references/jq-queries.md |
session |
Replay a session timeline with tools, tokens, timing | CC session JSONL | ${CLAUDE_PLUGIN_ROOT}/skills/analytics/references/session-replay.md |
cost |
Token cost estimation with cache savings | stats-cache.json |
${CLAUDE_PLUGIN_ROOT}/skills/analytics/references/cost-estimation.md |
trends |
Daily activity, model delegation, peak hours | stats-cache.json |
${CLAUDE_PLUGIN_ROOT}/skills/analytics/references/trends-analysis.md |
summary |
Unified view of all categories | All files | ${CLAUDE_PLUGIN_ROOT}/skills/analytics/references/jq-queries.md |
otel |
CC 2.1.117 + 2.1.122 + 2.1.126 OTEL enrichments: top slash commands (user vs model), per-effort cost, effort-vs-success correlation, skill activation by trigger type, most-mentioned @ targets |
~/.claude/otel/*.jsonl |
${CLAUDE_PLUGIN_ROOT}/skills/analytics/references/otel-fields.md |
What ships with it
14 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.
- references/cost-estimation.md 5.7 KB
- references/data-locations.md 2.3 KB
- references/jq-queries.md 5.6 KB
- references/otel-fields.md 13 KB
- references/session-replay.md 3.2 KB
- references/trends-analysis.md 2.0 KB
- rules/_sections.md 971 B
- rules/_template.md 339 B
- rules/cost-calculation.md 1.8 KB
- rules/data-privacy.md 1.6 KB
- rules/large-file-streaming.md 1.8 KB
- rules/visualization-dashboards.md 3.8 KB
- rules/visualization-recharts.md 3.9 KB
- test-cases.json 7.5 KB
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.
- today First seen · 144 lines · 62 tokens per session scan A 350318bdbcde
analytics is a skill published in the GitHub repository yonatangross/orchestkit (225 stars, last pushed today), licensed MIT. It adds 62 tokens to every session and 2,951 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
adapt-architecture
Execute structural metamorphosis using strangler fig migration, chrysalis phases, and interface preservation. Covers transformation planning, parallel running, progressive cutover, rollback design, and post-metamorphosis stabilization for system architecture evolution. Use when assess-form has classified the system as…
adaptic
Master skill composing the 5-step synoptic cycle for panoramic synthesis across multiple domains. Orchestrates meditate, expand-awareness, observe, awareness, integrate-gestalt, and express-insight into a coherent process that produces unified understanding rather than sequential compromise. Use when a problem…
add-puzzle-type
Scaffold a new puzzle type across all 10+ pipeline integration points in jigsawR. Creates the core puzzle module, wires it into the unified pipeline (generation, positioning, rendering, adjacency), adds ggpuzzle geom/stat layers, updates DESCRIPTION and config.yml, extends the Shiny app, and creates a comprehensive…
add-rcpp-integration
Add Rcpp or RcppArmadillo integration to an R package for high-performance C++ code. Covers setup, writing C++ functions, RcppExports generation, testing compiled code, and debugging. Use when an R function is too slow and profiling confirms a bottleneck, when you need to interface with existing C/C++ libraries, or…
aikido
Practice aikido as a defensive martial art emphasizing harmony, redirection, and controlled resolution. Covers centering and grounding, ukemi (safe falling and rolling), core techniques (irimi-nage, shiho-nage, kote-gaeshi, ikkyo), blending and tai sabaki (body movement), randori (multiple attacker practice), weapons…
analyze-codebase-for-mcp
Analyze an arbitrary codebase to identify functions, APIs, and data sources suitable for exposure as MCP tools, producing a tool specification document. Use when planning an MCP server for an existing project, auditing a codebase before wrapping it as an AI-accessible tool surface, comparing what a codebase can do…