Borrowing it
Nothing to install: this file belongs to searlsco/prove_it. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/searlsco/prove_it/main/.claude/skills/session-log/SKILL.mdgit clone --depth 1 https://github.com/searlsco/prove_itWrote 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/searlsco/prove_it/session-log)<a href="https://agentmods.dev/skills/searlsco/prove_it/session-log"><img src="https://agentmods.dev/badge/skills/searlsco/prove_it/session-log.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.1 | $0.00039 | $0.00493 |
| Opus 5 | $0.00019 | $0.00246 |
| Sonnet 5 | $0.00008 | $0.00099 |
| Haiku 4.5 | $0.00004 | $0.00049 |
Grade A, and why
session-log 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 7d 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
Inspect prove_it session logs
Session data lives in ~/.claude/prove_it/sessions/. Two file types per session:
<session_id>.json—session state (project dir, git HEAD, started_at)<session_id>.jsonl—reviewer log (one JSON object per line: at, reviewer, status, reason, projectDir, sessionId)_project_<hash>.jsonl—project-level reviewer log (when session_id was null)
Determine the current session ID
The current Claude Code session ID is passed in hook input. To find it for the active conversation, check the most recently modified .jsonl file:
ls -t ~/.claude/prove_it/sessions/*.jsonl | head -5
What to show
Default (no args): show the current session's reviewer log
- Find the most recently modified
.jsonlfile (excluding_project_*andtest-session*files). - Read it and display each entry as a table or formatted list showing:
- Time (human-readable from the
attimestamp) - Reviewer name
- Status (PASS/FAIL/SKIP/BOOM)
- Reason (the reviewer's rationale)
- Time (human-readable from the
With a session ID arg: show that specific session
Read <session_id>.jsonl and <session_id>.json and display both the session state and reviewer entries.
With --all or all: list all sessions
List all session .json files sorted by modification time, showing session ID, project, and started_at.
With --stats or stats: aggregate reviewer stats
Count PASS/FAIL/SKIP/BOOM across all .jsonl files and show totals.
Formatting
- Show timestamps as relative times (e.g., "2 min ago") or HH:MM:SS
- Truncate long reasons to ~120 chars in table view, show full text if only one session
- Use the reviewer name as-is (e.g., "coverage-review", "fast-tests")
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.
- 7d ago First seen · 50 lines · 39 tokens per session scan A 94b1bd9a69f8
session-log is a skill published in the GitHub repository searlsco/prove_it (199 stars, last pushed 4mo ago), licensed MIT. It adds 39 tokens to every session and 493 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-30.
Other skills, from other repositories
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
diagnose
Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.
repro-admin
Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
byted-util-volcengine-detect-retry
Orchestrates Volcengine Cloud Detect (云拨测) false-alarm reduction for failing periodic-task dial points. Use for scheduled task scans, retrying failed nodes, control-testing node health, distinguishing real target outages from broken dial points, and suggesting same-type LastMile/IDC/Private replacement nodes. Runs the…