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/nxtg-ai/forge-plugin/reportgit clone --depth 1 https://github.com/nxtg-ai/forge-pluginWhat 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.00000 | $0.01360 |
| Opus 5 | $0.00000 | $0.00680 |
| Sonnet 5 | $0.00000 | $0.00272 |
| Haiku 4.5 | $0.00000 | $0.00136 |
Grade A, and why
report 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.
How it starts
The opening of the file, as written. The whole thing — 142 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/forge:report
Generate a comprehensive session activity report from real git history, PR status, test results, governance changes, and checkpoint history.
| Level | L1 Vibe Coder |
| Category | State Management |
| Syntax | /forge:report [--brief] [--since <timespec>] [--json] [--branch <name>] |
What It Does
/forge:report builds an activity report from real project data. It pulls commits from git history, calculates lines changed, identifies the most-modified files, checks for open pull requests on the current branch, counts test files, reads governance sentinel log entries, and lists saved checkpoints. The result is a structured report that answers "what happened during this session?" with concrete data rather than memory.
The report works by default on the last 24 hours of activity, or since the current branch diverged from main. You can customize the window with --since to generate weekly, sprint, or custom-range reports. The brief mode gives you a one-liner summary; JSON mode gives you machine-readable output for integration with other tools.
Without this command, summarizing a session means scanning git log, counting changes manually, checking PR status separately, and trying to remember what governance decisions were made. /forge:report gathers all of this in parallel and presents it in a single document with recommendations for what to do next.
Syntax & Options
/forge:report [--brief] [--since <timespec>] [--json] [--branch <name>]
| Option | Description |
|---|---|
--brief or -b |
One-line summary: branch, commit count, files changed, lines, PR status, last commit |
--since <timespec> |
Activity since a specific time (e.g., "8 hours ago", yesterday, "7 days ago") |
--json |
Output all gathered data as a structured JSON object |
--branch <name> |
Report on a specific branch instead of the current one |
When to Use It
- End of day summary: Run it before closing your session to capture what was accomplished.
- Standup preparation: Use
--briefto get a quick summary for your daily standup. - Sprint retrospective: Use
--since "14 days ago"to generate a two-week activity report.
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 · 142 lines · 0 tokens per session scan A a2bcbeafd6f0
report is a command published in the GitHub repository nxtg-ai/forge-plugin (5 stars, last pushed 12d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,360 tokens. 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
paul:help
Show available PAUL commands and usage guide.
safe-refactor
Safe refactoring with automated review, testing, and rollback capabilities.
paul:verify
Guide manual user acceptance testing of recently built features.
expect
Diff-aware AI browser testing — reads the git diff, maps changes to affected pages via the route map, generates a targeted test plan, and executes it via agent-browser (Rust daemon + CDP, ARIA-tree-first) with pass/fail reporting. Use when testing UI changes, verifying PRs before merge, or running regression checks on…
kill-mutants
Analyze surviving mutants from a mutation testing run and write targeted unit tests to kill them. Re-runs mutations to confirm kills.
mutate
Run mutation testing to verify test quality. Builds a custom mutation tool or uses an existing framework, runs mutations, and reports the mutation score with surviving mutants.