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-deep-divenpx skills add slbug/claude-ruby-grape-rails --skill session-deep-divegit 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-deep-dive)<a href="https://agentmods.dev/skills/slbug/claude-ruby-grape-rails/session-deep-dive"><img src="https://agentmods.dev/badge/skills/slbug/claude-ruby-grape-rails/session-deep-dive.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.00036 | $0.00999 |
| Opus 5 | $0.00018 | $0.00500 |
| Sonnet 5 | $0.00007 | $0.00200 |
| Haiku 4.5 | $0.00004 | $0.00100 |
Grade A, and why
session-deep-dive 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 — 133 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Session Deep Dive (Tier 2)
Audience: Agents, Not Humans
Imperative-only. NOT a replacement for deterministic evals.
Requirements
ccriderCLI on PATH (full transcript export; resolves DB path internally)- populated
.claude/session-metrics/metrics.jsonlfrom/session-scan
| Missing | Action |
|---|---|
| ledger | tell contributor to run /session-scan first |
ccrider not on PATH |
ask contributor to install (https://github.com/neilberkman/ccrider) |
Usage
| Command | Behavior |
|---|---|
/session-deep-dive SESSION_ID |
analyze explicit session ID |
/session-deep-dive --last |
most recent session |
/session-deep-dive --from-scan |
sessions flagged by latest scan |
/session-deep-dive --from-scan --provider <NAME> |
scoped to provider |
/session-deep-dive --compare .claude/session-analysis/insights-2026-03-20.md |
comparison reference |
Workflow
1. Resolve Target Sessions
Selectors: explicit session ID, --last, --from-scan, optional
--provider NAME, optional --compare PATH.
--provider present → only analyze ledger entries with matching provider field.
2. Load Existing Metrics as Hints
For each target session, load ledger entry. Treat these values as starting hypotheses (NOT ground truth):
- friction score
- fingerprint
- plugin opportunity score
- tool profile
- skill-effectiveness hints
Confirm with transcript evidence before relying on them.
3. Export Transcripts via ccrider CLI
Use ccrider export — no MCP, no truncation, full session.
Per target:
mkdir -p .claude/session-analysisccrider export SESSION_ID --output .claude/session-analysis/{short_id}-transcript.md
Each exported file = complete session markdown (user, assistant, tool messages). Main context does NOT read these files — only the analysis subagent does.
Multiple sessions → loop selected IDs, invoke ccrider export per ID.
Avoids loading transcript bytes into main-context tool output.
4. Analyze Each Session
What ships with it
2 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.
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 · 133 lines · 36 tokens per session scan A bac6f18b3506
session-deep-dive is a skill published in the GitHub repository slbug/claude-ruby-grape-rails (7 stars, last pushed 4d ago), licensed MIT. It adds 36 tokens to every session and 999 once invoked, about $0.0002 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、自动化测试、运行态驱动、签名恢复、抓包分析.