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-scannpx skills add slbug/claude-ruby-grape-rails --skill session-scangit 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-scan)<a href="https://agentmods.dev/skills/slbug/claude-ruby-grape-rails/session-scan"><img src="https://agentmods.dev/badge/skills/slbug/claude-ruby-grape-rails/session-scan.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.00039 | $0.01224 |
| Opus 5 | $0.00019 | $0.00612 |
| Sonnet 5 | $0.00008 | $0.00245 |
| Haiku 4.5 | $0.00004 | $0.00122 |
Grade A, and why
session-scan 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 3d 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 — 124 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Session Scan (Tier 1)
Audience: Agents, Not Humans
Imperative-only. Contributor analytics, NOT release gating.
Requirements
| Requirement | Detail |
|---|---|
ccrider installed |
https://github.com/neilberkman/ccrider |
ccrider sync ran |
populates SQLite DB from CC / Codex session files |
| Python | 3.14+ (uses str | None / list[X] natively) |
DB Path Resolution
Search order:
--db PATHflagCCRIDER_DBenv var$XDG_CONFIG_HOME/ccrider/sessions.db$HOME/.config/ccrider/sessions.db(Linux / macOS default)$HOME/Library/Application Support/ccrider/sessions.db(macOS alt)$APPDATA/ccrider/sessions.db(Windows)
No candidate exists → script exits with code 2, lists tried paths.
Ask contributor for DB path, re-run with --db PATH. Do NOT hard-fail
until contributor confirms no path is available.
Usage
| Command | Behavior |
|---|---|
/session-scan |
default 7-day window |
/session-scan --since 2026-02-01 |
start date filter |
/session-scan --project myapp |
substring on project_path |
/session-scan --provider claude |
exact match on provider |
/session-scan --limit 20 |
cap candidate count |
/session-scan --list |
discovery only, no scoring |
/session-scan --rescan |
recompute already-scanned sessions |
/session-scan --db /custom/path/to/sessions.db |
DB override |
--provider takes exact sessions.provider value from --list
output. Examples (claude, codex, claude-code) are illustrative
— filter is exact match.
Main-Context Workflow
1. Parse Arguments
Pass $ARGUMENTS through to scan-sessions.py. Supported flags:
| Flag | Default |
|---|---|
--since DATE |
7 days ago |
--project SUBSTR |
matches sessions.project_path LIKE '%SUBSTR%' |
--provider NAME |
exact match on sessions.provider |
--limit N |
50 |
--list |
discovery only |
--rescan |
recompute scanned sessions |
--db PATH |
DB override |
--metrics-dir DIR |
.claude/session-metrics |
--min-messages N |
5 (filter trivial ping/hi sessions) |
What ships with it
3 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.
- 3d ago First seen · 124 lines · 39 tokens per session scan A 8f6d72bb0de5
session-scan is a skill published in the GitHub repository slbug/claude-ruby-grape-rails (7 stars, last pushed 4d ago), licensed MIT. It adds 39 tokens to every session and 1,224 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
ml-data-pipeline-architecture
Patterns for efficient ML data pipelines using Polars, Arrow, and ClickHouse. TRIGGERS - data pipeline, polars vs pandas, arrow format.
lineage
Use when user invokes /lineage with a column name (optionally qualified with table/schema). Also triggers on "trace this column", "where does X come from", "what reads from Y table". Traces column-level data lineage through SQL, Kafka, Spark, JDBC, and ORM codebases. Produces a structured lineage path with confidence…
nosql-database-design
Designs a NoSQL data model by leading with access pattern analysis. Covers DynamoDB single-table design (PK/SK/GSI) and MongoDB embedding vs referencing, consistency models, and capacity planning. Invoked when the user asks to design a DynamoDB schema, MongoDB data model, or NoSQL data model.
relational-database-design
Designs or reviews a relational database schema for a given domain. Covers table structure, normalization, indexes, constraints, and migration strategy. Invoked when the user asks to design a schema, review a database structure, or optimize a data model.
business-intelligence-pro
Activates BusinessIntelligence-Pro for KPI design, dashboard strategy, and SQL optimization. Use when you need north star metric and metric tree design, LookML or Looker explore architecture, complex SQL with window functions and CTEs, threshold-based and ML-powered alerting design, or data storytelling for executive…
Add Postgres-native vector retrieval to agent and RAG workflows with pgvector
Store embeddings beside application data in Postgres, create vector indexes, and query nearest neighbors for semantic search, RAG, recommendations, or agent memory retrieval.