AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Agent Usage Analyzer

skill-yctimlin-agent-usage-analyzer-agent-usage-analyzer · by yctimlin

Analyze local AI-agent session histories and report usage counts for agent skills, tools, commands, or MCP actions across sessions. Use for requests about skill rankings, top skills used last week, tool usage, recent-session comparisons, agent-specific usage, or exports from Codex, Claude Code, and other compatible JSON or JSONL agent-history exports. Read-only.

↗ Repository
— No reviews yet
0 installs
32 views
0.0% view→install

Install

$ agentstack add skill-yctimlin-agent-usage-analyzer-agent-usage-analyzer

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • ✓ Prompt-injection patterns
  • ✓ Secret / credential exfiltration
  • ✓ Dangerous shell & filesystem operations
  • ✓ Untrusted network calls
  • ✓ Known-malicious package signatures

What it can access

  • ✓ Network access No
  • ✓ Filesystem access No
  • ✓ Shell / process execution No
  • ✓ Environment & secrets No
  • ✓ Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-yctimlin-agent-usage-analyzer-agent-usage-analyzer)

Reliability & compatibility

✓ Security review passed
0 installs to date
— no reviews yet
○ 6mo ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Agent Usage Analyzer? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Agent Usage Analyzer

Goal

Produce an accurate, local, read-only report of structured skill, tool, command, and MCP usage across agent sessions.

Inputs to infer from the user's request

  • agent or source filters
  • since and until date filters
  • repo or cwd filters
  • raw versus canonical mode
  • kind filter
  • output format
  • whether the user supplied an export directory
  • whether samples, partial sessions, or heuristic parsing are allowed

Resources

  • Analyzer script: scripts/analyze.mjs
  • Install helper: scripts/install.mjs
  • Output contract: references/OUTPUT.md
  • Alias example: references/ALIASES.example.yaml

Workflow

  1. Do not count usage manually from transcript prose.
  2. Prefer running scripts/analyze.mjs.
  3. Use --provider auto unless the user supplied an explicit export directory.
  4. If the user asks for "skill usage", "agent skills", or named skill counts, prefer --kind skill.
  5. For Codex and Claude Code event-log exports, count skill usage from structured .../skills//SKILL.md load signals rather than generic transport tools.
  6. If the source only exposes tool or MCP events and does not expose any structured skill-load signal, say so explicitly instead of presenting tool counts as skill counts.
  7. If the analyzer reports missing prerequisites, explain what is missing instead of guessing.
  8. Present the result as a markdown table unless the user asked for JSON or CSV.
  9. Always state coverage and caveats.

Output rules

  • Treat skill, tool, command, and mcp as separate categories unless the user asks for a broader combined report.
  • Default to canonical mode.
  • Use raw mode only when the user asks for raw names.
  • Keep samples off unless the user asks for them.
  • Sort rows by invocation count descending.
  • Never imply skipped sessions were counted.
  • When reporting skill usage from Codex or Claude Code archives, note that counts come from structured skill-load records, typically reads or prompts that reference SKILL.md.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Write a review

Versions

  • v0.1.0 Imported from the upstream source.

More in Data & Analytics