Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/dimetron/pi-gonpx agentmods add skills/dimetron/pi-go/pi-check-session-logsWrote 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/dimetron/pi-go/pi-check-session-logs)<a href="https://agentmods.dev/skills/dimetron/pi-go/pi-check-session-logs"><img src="https://agentmods.dev/badge/skills/dimetron/pi-go/pi-check-session-logs/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/dimetron/pi-go/pi-check-session-logs"><img src="https://agentmods.dev/badge/skills/dimetron/pi-go/pi-check-session-logs.svg" alt="Reviewed on agentmods" width="80" 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.00039 | $0.00549 |
| Opus 5 | $0.00019 | $0.00275 |
| Sonnet 5 | $0.00008 | $0.00110 |
| Haiku 4.5 | $0.00004 | $0.00055 |
Grade A, and why
pi-check-session-logs 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 9d 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 — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Check Session Logs
Scan recent pi-go session logs for tool call errors, deduplicate by pattern, and present results.
Steps
- Run the analysis script (scans last 24h by default, override with
HOURS=N):
bash .pi-go/skills/pi-check-session-logs/analyze.sh
To scan a different time window:
HOURS=48 bash .pi-go/skills/pi-check-session-logs/analyze.sh
-
Present the raw output to the user as-is — the script already formats a markdown table.
-
Suggest optimizations based on the error patterns:
- For "not found" errors: suggest better path resolution or fallback logic
- For "permission denied": suggest sandbox configuration changes
- For "exit code" failures: suggest build/test fixes
- For repeated tool errors: suggest system prompt improvements to avoid the pattern
- For STREAM_ERROR: suggest retry/reconnect improvements
-
Extract actionable fixes — After presenting the summary, create (or update) an actionable fixes document:
mkdir -p ./specs/issues/001-session-errors echo "<research>" > ./specs/issues/001-session-errors/PROMPT.mdThis file should contain a prompt that can be loaded to guide the agent toward fixing the detected error patterns. Structure it with sections for:
- The top N error patterns are detected (with specific examples)
- Corresponding fix suggestions per pattern
- Context about when each fix applies (which tools, which scenarios)
Use this format for the prompt file:
# Session Error Fix Prompts ## Pattern: [error name] - **Detected in**: [sessions/files where found] - **Fix suggestion**: [specific actionable steps]If the file already exists, update it to include new patterns while preserving existing ones.
Examples
/pi-check-session-logs— Analyze logs from last 24h/pi-check-session-logs HOURS=48— Analyze logs from last 48h
- Run the analysis for the findings
Research on each issue using subagent - for each issue with priority, score, if it's going to be implemented or rejected.
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.
- 9d ago First seen · 66 lines · 39 tokens per session scan A dbf83acb1d58
pi-check-session-logs is a skill published in the GitHub repository dimetron/pi-go (155 stars, last pushed yesterday), licensed MIT. It adds 39 tokens to every session and 549 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
use-modern-go
Use the Modern Go Guidelines CLI whenever writing, modifying, fixing, or refactoring Go code. Apply its version-specific guidance to generated changes.
gograph
Go repository intelligence for Claude Code. Use when reading, navigating, editing, reviewing, or refactoring a Go codebase. Exposes 64 query, analysis, and workflow capabilities through the local gograph MCP server, including bounded first-call exploration, AST-aware call graphs, blast-radius analysis, impact, and…
go
Use when writing, reviewing, testing, or shipping Go code and HTTP services: idioms, %w error wrapping, goroutine/context/errgroup concurrency, net/http 1.22 routing, log/slog, project layout, table-driven tests, Go hardening. NOT language-agnostic threat modeling (that is secure-coding), NOT Dockerfile/CI shipping…
code-review-go
Deep Go-specific code review covering goroutine lifecycle, data races, error wrapping, domain modeling, and interface design. Applied in addition to the generic code-review skill when Go code is detected. Invoked when reviewing Go PRs, Go code changes, or performing Go-specific quality checks.
toolchains-golang-core
Go 1.22-1.24 core patterns for minimalism, efficiency, code reuse, and performance.
cli-to-go-migration
Reusable agent skill for migrating command-line interfaces from any programming language to Go.