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 skills add nicknisi/sessions --skill session-metricsgit clone --depth 1 https://github.com/nicknisi/sessionsWrote 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/nicknisi/sessions/session-metrics)<a href="https://agentmods.dev/skills/nicknisi/sessions/session-metrics"><img src="https://agentmods.dev/badge/skills/nicknisi/sessions/session-metrics.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.1 | $0.00062 | $0.00404 |
| Opus 5 | $0.00031 | $0.00202 |
| Sonnet 5 | $0.00012 | $0.00081 |
| Haiku 4.5 | $0.00006 | $0.00040 |
Grade A, and why
session-metrics 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 8d 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.
What it actually says
Show session usage metrics and analytics.
Steps
-
Parse the time period. Convert the user's argument to a date range (YYYY-MM-DD). Default to the past 7 days if no period specified. Common inputs: "past week", "this month", "past 30 days", "may 2026".
-
Fetch metrics. Call
get_session_metricswith:startDateandendDatefrom the parsed range
-
Format the dashboard:
Session Metrics: {start} to {end}
Overview
- {total sessions} sessions | {total messages} messages
- Tools: {breakdown with counts}
Top Projects (table: project, sessions, messages) List the top 10 by session count.
Daily Activity (table or mini-chart: date, sessions, messages) Show each day in the range.
Active Hours Render the hours heatmap as a simple bar chart or table showing which hours of the day have the most sessions. Convert to local time labels (e.g., "9am", "2pm").
Guidelines
- Round percentages to whole numbers.
- For active hours, group into time blocks if the data is sparse (morning/afternoon/evening/night).
- If a tool has zero sessions, omit it from the breakdown.
- Keep the formatting clean — this should be pasteable into a document or message.
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.
- 8d ago First seen · 43 lines · 62 tokens per session scan A 49dc8368f061
session-metrics is a skill published in the GitHub repository nicknisi/sessions (30 stars, last pushed 6d ago), licensed MIT. It adds 62 tokens to every session and 404 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
rework-rate
Measure and interpret PR rework rate — the emerging 5th DORA metric.
work
Execute an approved wish plan — orchestrate subagents per task group with fix loops, validation, and review handoff.
trace
Dispatch trace subagent to investigate unknown issues — reproduces, traces, and reports root cause for fix handoff.
preview-design
Render a real artifact through this branch's local MERIDIAN design code (not the published npm package) so the team can test the new Design Convention on the document / handoff / platform surfaces before it ships. Use for /preview-design, "preview the design convention", "render this with the new design", or Design…
sw-do
Implement a SpecWeave increment task by task through the ledger, with evidence per task and a verified close. Use for "implement this", "start working", "continue the increment", "keep going".
done
Close an increment: ledger check, specweave verify, optional review, then specweave complete. Use when all tasks are done and saying "close increment", "we are done", or "finish up".