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.
git 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/commands/luiseiman/dotforge/cap)<a href="https://agentmods.dev/commands/luiseiman/dotforge/cap"><img src="https://agentmods.dev/badge/commands/luiseiman/dotforge/cap/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/commands/luiseiman/dotforge/cap"><img src="https://agentmods.dev/badge/commands/luiseiman/dotforge/cap.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.00019 | $0.00065 |
| Opus 5.5 | $0.00008 | $0.00026 |
| Sonnet 5.5 | $0.00004 | $0.00013 |
| Haiku 4.5 | $0.00002 | $0.00006 |
Grade A, and why
cap 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 1mo 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 capture with $ARGUMENTS. Pass-through alias to reduce friction.
If $ARGUMENTS is empty, run /forge capture with no arguments (auto-detect mode).
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.
- 1mo ago First seen · 9 lines · 19 tokens per session scan A 3b6baf663ff8
cap is a command published in the GitHub repository luiseiman/dotforge (8 stars, last pushed 9d ago), licensed MIT. It adds 19 tokens to every session and 65 once invoked, about $0.0001 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 commands, from other repositories
retex
Retex - Capture lesson learned dans memory après fix, rollback, erreur.
context-stats
Display context window usage and token statistics.
handoff
Write a session handoff document for continuity.
argos
A command for checking whether an implementation matches its design deliverables. Its Korean description compares the work to the design as part of a completion inspection.
ccc-context-budget
Show how full the context window is, which components use the most of it, and when to save the session and compact. Use when the session feels slow, long or near its context limit.
lessons
Lists the feedback memories captured for the current project (and globally) — the "lessons" learned from user corrections.