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/luiseiman/dotforge/session-insightsnpx 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.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.00018 | $0.01290 |
| Opus 5 | $0.00009 | $0.00645 |
| Sonnet 5 | $0.00004 | $0.00258 |
| Haiku 4.5 | $0.00002 | $0.00129 |
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 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 — 134 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.
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.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 → cross-reference
git log --name-onlyagainst.claude/rules/*.mdglobs to estimate historical rule coverage
Mark all retroactive data clearly as:
⚠ Inferred from git history — no session metrics available yet.
Session metrics will accumulate automatically after /forge sync.
Step 2: Compute metrics
From available data, calculate:
Session Metrics (from ~/.claude/metrics/)
When JSON metrics files exist, aggregate across the last N sessions (default 20):
- Total sessions: count of metric files
- Avg files touched: mean files_touched per session
- Avg hook blocks: mean hook_blocks + lint_blocks (lower is better — team is learning)
- Rule coverage trend: plot rule_coverage over time (improving / stable / declining)
- Error rate: errors_added / sessions (target: < 0.5)
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 · 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 2mo ago), licensed MIT. It adds 18 tokens to every session and 1,290 once invoked, about $0.0001 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
scaffold
Set up or align a non-code ops/PM repo with the ops folder structure, CLAUDE.md, and INDEX.md hierarchy.
find-opps
Find new directions for an ops project — adjacent opportunities, strategic gaps, preparatory research. Use when known work is well-mined and you need to look outward.
prioritize
Pick 2–3 independent ops tasks from active plans and backlog for autonomous execution, weighing impact, feasibility, and project goals.
factory-db-migration
The operational discipline for running a destructive change against a production database — schema migrations, data backfills, one-shot RPCs, historical seed imports. Adjacent to factory-data-layer.md (schema design) and factory-deployment.md (where migrations execute in CI) — this skill is about the runbook around…
factory-api
API conventions for both server actions and tRPC builds. Covers the decision between them, per-mutation Zod input schemas, central router composition, pagination shape, multi-field search via Drizzle ilike + or(), mutation lifecycle hooks, conditional query enabling, stale-time defaults, error response shape and…
factory-auth
Auth and authorization conventions distilled across builds with three different auth stacks (Better Auth + orgs, Supabase Auth + RLS, Clerk). Covers the provider decision matrix, the unified wrapper interface (requireAuth / requireRole / withOrgContext), procedure tier stacking, session handling, OAuth callback…