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/slbug/claude-ruby-grape-rails/session-trendsnpx skills add slbug/claude-ruby-grape-rails --skill session-trendsgit clone --depth 1 https://github.com/slbug/claude-ruby-grape-railsWrote 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/slbug/claude-ruby-grape-rails/session-trends)<a href="https://agentmods.dev/skills/slbug/claude-ruby-grape-rails/session-trends"><img src="https://agentmods.dev/badge/skills/slbug/claude-ruby-grape-rails/session-trends.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.00029 | $0.00785 |
| Opus 5 | $0.00015 | $0.00392 |
| Sonnet 5 | $0.00006 | $0.00157 |
| Haiku 4.5 | $0.00003 | $0.00078 |
Grade A, and why
session-trends 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 4d 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.
Session Trends
Audience: Agents, Not Humans
Imperative-only. Output is monitoring + prioritization signal — NOT causal proof of plugin impact.
Requirements
.claude/session-metrics/metrics.jsonl (from /session-scan).
Usage
| Command | Behavior |
|---|---|
/session-trends |
default 7-day window |
/session-trends --window 30d |
broader window |
/session-trends --project myapp |
substring on project_path |
/session-trends --provider claude-code |
exact provider |
/session-trends --compare .claude/session-analysis/insights-2026-03-20.md |
comparison reference |
Workflow
1. Parse Arguments
| Flag | Values |
|---|---|
--window |
7d / 30d / all |
--project |
NAME |
--provider |
NAME |
--compare |
PATH |
2. Read the Metrics Ledger
Read .claude/session-metrics/metrics.jsonl. Missing or empty → stop;
tell contributor to run /session-scan first.
3. Compute Windowed Aggregates
Run python3 .claude/skills/session-scan/references/compute-metrics.py --trends .claude/session-metrics/metrics.jsonl from repo root.
Add --project "$PROJECT_FILTER" or --provider "$PROVIDER_FILTER"
only when the contributor requested those filters.
4. Read Comparison Notes Separately
--compare PATH provided → read separately, compare cautiously against
computed aggregates. Do NOT rely on MEMORY.md as a required baseline.
5. Present a Readable Report
Show:
- top-level
time_series_signal - distinct dates represented in ledger
- total sessions in each window
- average friction
- average opportunity
- fingerprint distribution
- Tier 2 eligible percentage
- plugin adoption rate
- provider distribution
Provider filter not used + ledger mixes providers → state explicitly before interpreting trends.
Brand-new ledger or fewer than 10 sessions:
- state explicitly: little or no time-series signal yet
- note when
7d,30d,allare effectively the same dataset - treat output as early snapshot, NOT a trend
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.
- 4d ago First seen · 107 lines · 29 tokens per session scan A 984e12994213
session-trends is a skill published in the GitHub repository slbug/claude-ruby-grape-rails (7 stars, last pushed 5d ago), licensed MIT. It adds 29 tokens to every session and 785 once invoked, about $0.0001 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-31.
Other skills, from other repositories
opencli-sitemap-author
Use when creating or maintaining OpenCLI site sitemaps: agent-facing navigation, page-state, action, workflow, API-reference, pitfall, and fallback knowledge for a website. Use after browser exploration discovers durable site context, when a sitemap is stale, or when promoting local site knowledge into the repo.
golden-rss
Use when testing the rss golden build.
overleaf-sync
Two-way sync between a local paper directory and an Overleaf project, so ARIS audit/edit workflows stay on the local copy while collaborators edit in the Overleaf web UI. Use when user says "同步 overleaf", "overleaf sync", "推送到 overleaf", "connect overleaf", "Overleaf 桥接", "pull overleaf", "push overleaf", or wants to…
omh-code-review
This is a Hermes-native code-review workflow skill.
redteam-web-detail-pack
Routing and boundary guidance for authorized general web application security testing. Use as a web testing router when the attack surface should be dispatched to more specific web vulnerability skills.
android-pentest
安卓应用渗透测试 — APK分析、Hook、自动化测试、运行态驱动、签名恢复、抓包分析.