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 commands/luiseiman/dotforge/forge-insightsgit clone --depth 1 https://github.com/luiseiman/dotforgeWhat 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.00016 | $0.00056 |
| Opus 5 | $0.00008 | $0.00028 |
| Sonnet 5 | $0.00003 | $0.00011 |
| Haiku 4.5 | $0.00002 | $0.00006 |
Grade A, and why
forge-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 2d 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.
What it actually says
Run /forge insights. Analyze CLAUDE_ERRORS.md, git history, and registry data to extract patterns. Generate actionable recommendations and feed them into the practices pipeline.
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.
- 2d ago First seen · 7 lines · 16 tokens per session scan A 043b9a9b397e
forge-insights is a command published in the GitHub repository luiseiman/dotforge (8 stars, last pushed 2mo ago), licensed MIT. It adds 16 tokens to every session and 56 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 commands, from other repositories
get-to-work
Autonomous ops work. Args: [mode] [repeat]. Modes: tasks | opps | full | escalating (default). Repeat: cycle (keep going, default) | once (single pass). Run this before stepping away from an ops repo.
recap
Summarize what happened in the project since a given date. Produces a short lead on what's different now, backed by tables and lists covering completed work, state changes, backlog movement, and key decisions. Use when the user wants to catch up on project activity, review recent progress, or generate a status update…
whats-next
Generate an executive overview of the project. Synthesizes state, backlogs, and recent plans into a ranked action plan answering "What should we do next?".
batch-execute
Execute a batch of ops plans continuously without user input, storing any issues and user questions in a .md file to be processed with the user afterwards. Do NOT invoke this yourself! Should only be invoked by the user.
batch-plan
Create a batch of ops plans continuously without user input, storing any user questions in a .md file to be processed with the user afterwards. Do NOT invoke this yourself! Should only be invoked by the user.
find-all
Run both ops finders in parallel (tasks, opps) and brief you on what they found. Discovery only — no plans, no execution.