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 skills add luiseiman/dotforge --skill session-insightsgit clone --depth 1 https://github.com/luiseiman/dotforgeWrote 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/luiseiman/dotforge/session-insights)<a href="https://agentmods.dev/skills/luiseiman/dotforge/session-insights"><img src="https://agentmods.dev/badge/skills/luiseiman/dotforge/session-insights/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/luiseiman/dotforge/session-insights"><img src="https://agentmods.dev/badge/skills/luiseiman/dotforge/session-insights.svg" alt="Reviewed on agentmods" width="80" 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.00046 | $0.01473 |
| Opus 5.5 | $0.00018 | $0.00589 |
| Sonnet 5.5 | $0.00009 | $0.00295 |
| Haiku 4.5 | $0.00005 | $0.00147 |
Grade A, and why
session-insights 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 17d 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 — 136 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Session Insights
Analyze the current project's Claude Code usage patterns and generate actionable recommendations.
Scope (native-first boundary, v4.7.0): Claude Code's /insights already analyzes up to 200 recent sessions across every project on the machine from transcripts (misunderstood requests, buggy code, auto-mode recommendation) → ~/.claude/usage-data/report.html. This skill does NOT read transcripts and does not duplicate that. It covers only what native has no access to: CLAUDE_ERRORS.md by Area/Type, session-report.sh hook metrics, .claude/agent-memory/, the registry score trend, and the automatic feed into practices/inbox/. Start by pointing the user to /insights for the cross-project friction picture.
Step 1: Gather session data
Collect data from available sources in the current project:
- Session metrics —
~/.claude/metrics/{project-slug}/*.json(structured JSON from session-report hook) - CLAUDE_ERRORS.md — error frequency by Area and Type
- Git log — files most frequently modified in commits mentioning "fix", "bug", "error"
- .claude/agent-memory/ — learnings accumulated by agents
- Registry history — audit score trend from
$DOTFORGE_DIR/registry/projects.local.yml
If a source doesn't exist, skip it and note as "unavailable".
Retroactive Analysis (no session metrics yet)
When ~/.claude/metrics/{project-slug}/ is empty or doesn't exist, reconstruct a pseudo-historical picture:
- CLAUDE_ERRORS.md → parse dates and group errors by week/month to show trends
- Git log →
git log --name-only --since="60 days ago"to identify:- Hot files (most frequently changed)
- Fix frequency (
git log --grep="fix" --oneline | wc -l) - Commit cadence by week
- Registry history → score progression over time
- Rule glob coverage → delegate to
/forge rule-check(therule-effectivenessskill) instead of recomputing it here; cite its ACTIVE/INERT summary
Mark all retroactive data clearly as:
⚠ Inferred from git history — no session metrics available yet.
Session metrics will accumulate automatically after /forge sync.
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.
- 17d ago Changed · +2 lines · +28 tokens per session 460872d1162f
- 1mo ago First seen · 134 lines · 18 tokens per session scan A 5e79c989af30
session-insights is a skill published in the GitHub repository luiseiman/dotforge (8 stars, last pushed 18d ago), licensed MIT. It adds 46 tokens to every session and 1,473 once invoked, about $0.0002 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-08-31.
Other skills, from other repositories
zephermine
Creates a persisted, sectionized implementation artifact suite through research, stakeholder interviews, domain analysis, database and API design, and multi-LLM review. Use for feature or product plans consumed by downstream implementation and QA. Prefer lightweight native plan/interview workflows for small tasks; on…
agent-team
A guide for coordinating a team of coding agents working on one task. It covers when to split work into parallel assignments, how a lead agent coordinates them, and how to record shared knowledge.
clio
A final-review and document-production workflow. It checks whether a process is ready to proceed, extracts source-based diagrams, and creates documents such as product requirements, technical documentation, and manuals.
design-plan
A design-system planning and implementation guide for frontend projects. A design system is a shared set of visual rules, reusable components, and accessibility practices for building consistent user interfaces.
frontend-design
A frontend design and implementation guide for turning a visual design plan into a working web interface. It also provides fallback guidance when an official design plugin is unavailable.
argos
A software inspection skill that checks an implementation against design documents such as API specifications, quality-assurance scenarios, flow diagrams, and other project specifications.