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/hamchowderr/braynee/insightfulnpx skills add hamchowderr/braynee --skill insightfulgit clone --depth 1 https://github.com/hamchowderr/brayneeWrote 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/hamchowderr/braynee/insightful)<a href="https://agentmods.dev/skills/hamchowderr/braynee/insightful"><img src="https://agentmods.dev/badge/skills/hamchowderr/braynee/insightful.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.00104 | $0.09709 |
| Opus 5 | $0.00052 | $0.04855 |
| Sonnet 5 | $0.00021 | $0.01942 |
| Haiku 4.5 | $0.00010 | $0.00971 |
Grade A, and why
insightful 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 — 493 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Insightful — Complete Claude Code Usage Report
Generate a comprehensive HTML insights report covering every Claude Code conversation across all projects. This skill produces a report matching the depth and quality of the built-in /insights command — with the same structured analysis stages — but covering ALL sessions ever, not just recent ones.
How Insightful differs from /insights
Built-in /insights |
Insightful | |
|---|---|---|
| Scope | Recent sessions only | Every session ever recorded |
| Data sources | stats-cache + recent facets | 5 sources: history.jsonl, stats-cache, facets, session indexes, .jsonl transcripts |
| Git commits | Not tracked | Detected from Bash tool calls in .jsonl files |
| Hours spent | Not tracked | Calculated from session timestamps |
| Multi-clauding | Not analyzed | Detects concurrent session overlaps |
| Notable sessions | Not included | Top 5 most intense sessions highlighted |
| Evolution | Not tracked | Month-over-month usage trends |
| Pre-tracking data | Invisible | Recovers sessions from before stats-cache existed |
| Output | In-terminal summary | Interactive HTML report with charts, copy buttons, collapsible sections |
Step 0: Backfill Facets (first-time setup)
Facets are qualitative per-session analysis files (goal, outcome, satisfaction, friction, helpfulness). Claude Code generates them automatically going forward, but older sessions may not have them — which means gaps in satisfaction and friction analysis.
Run the collect script first to check coverage:
node "${CLAUDE_PLUGIN_ROOT}/skills/insightful/collect-insights.js"
If it prints a ⚠️ FACET COVERAGE LOW warning, backfill your historical sessions before generating the report. Backfill uses claude -p (your Claude Code subscription) — no API billing.
# Dry run — shows what would be processed, no LLM calls
node "${CLAUDE_PLUGIN_ROOT}/skills/insightful/backfill-facets.mjs" --dry-run
# Run first 50 sessions
node "${CLAUDE_PLUGIN_ROOT}/skills/insightful/backfill-facets.mjs" --chunk=50
# Run all remaining
node "${CLAUDE_PLUGIN_ROOT}/skills/insightful/backfill-facets.mjs" --chunk=500
What ships with it
2 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 · 493 lines · 104 tokens per session scan A d030fbae0311
insightful is a skill published in the GitHub repository hamchowderr/braynee (2 stars, last pushed 7d ago), licensed MIT. It adds 104 tokens to every session and 9,709 once invoked, about $0.0005 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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.
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…