ai-engineering-fluency: Skill for Claude Code

.claude/skills/session-log-data/SKILL.md

session-log-data is a skill for Claude Code from rajbos/ai-engineering-fluency. It costs 35 tokens per session (2,088 once invoked), scanned A, original, MIT.

A reference guide to session-log and usage-data files made available in the coding-agent environment after setup. Session logs record AI-coding conversations, models, and tool calls, while aggregated data can support usage analysis.

In plain words
What is it for?
Use it when analyzing token usage, model use, estimated costs, reports, or debugging information from downloaded logs.
Why use it?
It explains what data is available and where to find it, including the case where cloud storage has not been configured.

Skill for Claude Code

Written for Claude Code: installed under .claude/. Also seen: mentions Claude Code.

This is rajbos/ai-engineering-fluency's own configuration. It tells Claude Code how to work on ai-engineering-fluency itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything ai-engineering-fluency configures →

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is ./session-logs/.

Reuse

Borrowing it

Nothing to install: this file belongs to rajbos/ai-engineering-fluency. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/rajbos/ai-engineering-fluency/main/.claude/skills/session-log-data/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/rajbos/ai-engineering-fluency

Made for: Claude Code.

Wrote 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.

agentmods badge for session-log-data

README.md
[![agentmods](https://agentmods.dev/badge/skills/rajbos/ai-engineering-fluency/session-log-data/github.svg)](https://agentmods.dev/skills/rajbos/ai-engineering-fluency/session-log-data)
Your own site
<a href="https://agentmods.dev/skills/rajbos/ai-engineering-fluency/session-log-data"><img src="https://agentmods.dev/badge/skills/rajbos/ai-engineering-fluency/session-log-data/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.

agentmods 80×15 button for session-log-data

Your own site · 80×15
<a href="https://agentmods.dev/skills/rajbos/ai-engineering-fluency/session-log-data"><img src="https://agentmods.dev/badge/skills/rajbos/ai-engineering-fluency/session-log-data.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 35 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,088 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00035 $0.02088
Opus 5.5 $0.00014 $0.00835
Sonnet 5.5 $0.00007 $0.00418
Haiku 4.5 $0.00003 $0.00209

Measured yesterday against content hash 30c85c53fc92, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

session-log-data 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 yesterday.

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.

.claude/skills/session-log-data/SKILL.md · 202 lines

How it starts

The opening of the file, as written. The whole thing — 202 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Session Log Data Skill

This skill describes the data files that are automatically downloaded into the GitHub Copilot Coding Agent environment during setup. These files are available for analysis, reporting, and debugging tasks.

When to Use This Skill

Use this skill when you need to:

  • Analyze Copilot token usage patterns from downloaded data
  • Generate reports or summaries from session logs or aggregated data
  • Debug token tracking or usage issues using real data
  • Understand model usage distribution across a team
  • Calculate estimated costs from usage data

Data Availability

These files are only present when the coding agent environment has Azure Storage configured via the copilot GitHub environment. If the files don't exist, Azure Storage is not configured for this repository.

Data Sources

1. Session Log Files — ./session-logs/

What: Raw AI-coding session log files (Copilot Chat, Copilot CLI, Claude Code/Desktop and other supported editors) downloaded from Azure Blob Storage. These contain the full conversation history including prompts, responses, model information, and tool calls.

Structure:

./session-logs/
└── {datasetId}/
    └── {machineId}/
        └── {YYYY-MM-DD}/
            ├── session-abc123.json
            └── 3a364aa6-b270-4d67-b1df-39841ccb74b0.jsonl

Date range: Last 7 days of session data.

File formats: Files arrive as .json and .jsonl, decompressed from .gz uploads or downloaded as-is when the uploader's blobCompressFiles setting is off. A download contains both formats, and in recent data nearly all of them are .jsonl. Always search for both extensions; a *.json-only search silently skips most sessions.

  • .jsonl — one JSON event per line. The event shape depends on the editor that wrote it (Claude Code/Desktop, Copilot CLI, VS Code Chat delta logs, ...), so look up the file's editor in the editor type manifest and its schema under docs/logFilesSchema/. For token and model numbers, prefer the shared parsers in the repo-root src/ (estimateTokensFromJsonlSession(), getModelUsageFromSession()) over hand-rolled jq.
  • .json — a whole Copilot Chat session in one document, with this structure:

Read the full file on GitHub · 202 lines

Changes

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.

  1. yesterday First seen · 202 lines · 35 tokens per session scan A 30c85c53fc92

Subscribe to this mod's changes

session-log-data is a skill published in the GitHub repository rajbos/ai-engineering-fluency (119 stars, last pushed yesterday), licensed MIT. It adds 35 tokens to every session and 2,088 once invoked, about $0.0001 per session on Opus 5.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-10-26.

Related

Other skills, from other repositories

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens