Analyze OpenCode session memory for usage patterns, costs, and history.
npx skills add https://github.com/kalindudc/shell --skill memory-analyzer
Please help me install this Agent Skill. Skill: memory-analyzer Source: https://github.com/kalindudc/shell/tree/main/home/.config/opencode/skills/memory-analyzer Command: npx skills add https://github.com/kalindudc/shell --skill memory-analyzer
Analyze OpenCode session memory to answer questions about usage patterns, costs, and history in a read-only manner that preserves data integrity.
Run the memory-analyzer to scan ~/.config/opencode/memory and generate a summary report.
High-intent search queries and answers about installing and using this skill.
Session memory analysis works by reading index.json for aggregate metrics, scanning per-session JSON files for detailed token and duration data, and grepping .md logs for historical conversations. This read-only approach computes usage patterns and costs while preserving data integrity.
You can extract aggregate metrics like session counts, model usage frequency, and skill or command frequency by reading the index.json file. This provides a high-level summary of usage patterns across your OpenCode session memory directory.
To start analyzing session memory, run the memory-analyzer to scan the ~/.config/opencode/memory directory. It will read the index.json, individual session JSON files, and .md logs to generate a comprehensive summary report of your usage patterns and costs.
The analysis covers per-session JSON files containing detailed metrics such as tokens, session duration, tools used, and accessed files. By scanning these individual session files, you can tie specific usage results and token costs directly to their corresponding projects.
Memory log analysis is limited to read-only operations, meaning it cannot modify, delete, or write to the session memory files. It strictly reads index.json, per-session JSON files, and .md logs to ensure complete data integrity during the usage analysis process.
DubibubiiAnalyze local JSONL logs to measure token usage by model, project, and day.
ericwang915Aggregate token usage and API costs from the usage history log.
aresbitSearch and analyze historical session JSONL files using jq and rg.
Tyler-R-KendrickParse local JSONL session logs to report token usage and session savings.
