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/nxtg-ai/forge-pluginWrote 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/nxtg-ai/forge-plugin/report)<a href="https://agentmods.dev/commands/nxtg-ai/forge-plugin/report"><img src="https://agentmods.dev/badge/commands/nxtg-ai/forge-plugin/report/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/nxtg-ai/forge-plugin/report"><img src="https://agentmods.dev/badge/commands/nxtg-ai/forge-plugin/report.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.00005 | $0.01148 |
| Opus 5.5 | $0.00002 | $0.00459 |
| Sonnet 5.5 | $0.00001 | $0.00230 |
| Haiku 4.5 | $0.00001 | $0.00115 |
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 12d 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 — 175 lines — stays where its author put it; the contents beside it link to each section on GitHub.
NXTG-Forge Session Report
You are the Session Reporter - generate a comprehensive activity report from real git history and project state.
Parse Arguments
Arguments received: $ARGUMENTS
Options:
- No arguments: Full report for current session/branch
--briefor-b: Brief summary only--since <timespec>: Activity since time (e.g.,--since "8 hours ago",--since yesterday)--json: Output as JSON--branch <name>: Report on specific branch (default: current)
Data Gathering
Gather all data using native tools. Execute these in parallel where possible:
1. Git Activity
# Current branch
git branch --show-current
# Commits (default: last 24 hours or since branch diverged from main)
git log --oneline --since="24 hours ago" 2>/dev/null || git log --oneline -20
# Detailed commit info
git log --format="%h %s (%cr) <%an>" --since="24 hours ago" 2>/dev/null || git log --format="%h %s (%cr) <%an>" -20
# Files changed
git diff --stat main...HEAD 2>/dev/null || git diff --stat HEAD~5..HEAD
# Insertions/deletions
git diff --shortstat main...HEAD 2>/dev/null || git diff --shortstat HEAD~5..HEAD
2. PR Status (if applicable)
# Check for open PRs from current branch
gh pr list --head "$(git branch --show-current)" --json number,title,state,url,checks 2>/dev/null
3. Test Status
# Quick test count
find src -name "*.test.ts" -o -name "*.spec.ts" 2>/dev/null | wc -l
4. Governance Changes
Read .claude/governance.json and check the sentinel log for recent entries.
5. Checkpoint History
ls -la .claude/checkpoints/*.json 2>/dev/null
Display Format
Brief Summary (--brief)
NXTG-Forge Session Summary
============================
Branch: {branch}
Commits: {count} | Files changed: {count} | +{insertions}/-{deletions}
Tests: {test_file_count} test files
PR: {pr_status or "None"}
Last commit: {hash} {message} ({time_ago})
Full Report (default)
NXTG-Forge Session Report
============================
Generated: {timestamp}
SESSION OVERVIEW
Branch: {branch}
Duration: {time_since_first_commit} (approx)
Commits: {commit_count}
Files changed: {files_changed}
Lines: +{insertions} / -{deletions}
GIT ACTIVITY
{hash} {message} ({time_ago})
{hash} {message} ({time_ago})
{hash} {message} ({time_ago})
...
Files most changed:
{file}: +{ins}/-{del}
{file}: +{ins}/-{del}
{file}: +{ins}/-{del}
{if PR exists}
PULL REQUEST
#{number}: {title}
URL: {url}
Status: {state}
Checks: {check_status}
{/if}
TESTS
Test files: {count}
{If test results available, show pass/fail summary}
GOVERNANCE
Status: {constitution_status}
Sentinel entries: {recent_count} recent
{List last 3 sentinel entries if available}
{if checkpoints exist}
CHECKPOINTS
{checkpoint_id} - {timestamp}
...
{/if}
RECOMMENDATIONS
Based on the session activity:
1. {recommendation based on what was done}
2. {recommendation based on gaps found}
3. {recommendation for next steps}
---
Next steps:
/nxtg-forge:status Check current state
/nxtg-forge:test Run test suite
/nxtg-forge:checkpoint Save checkpoint
/nxtg-forge:gap-analysis Identify remaining gaps
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.
- 12d ago Changed a078cf82bc18
- 1mo ago Changed · +33 lines · +5 tokens per session 475a70336f98
- 1mo 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 (6 stars, last pushed 4d ago), licensed MIT. It adds 5 tokens to every session and 1,148 once invoked, about $0.0000 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
fix-issues
Diagnose, reproduce, then fix reproducible open GitHub issues in parallel: one clean worktree/issue; symlink build artifacts to avoid rebuilds.
release
Release all packages at specified version.
pr
Prepare a clear, reviewer-friendly pull request for the committed work on the current branch. You never modify source files, and you never push, create, edit, or comment on the pull request yourself: your one write, when this run opens a pull request, is the body file below. The node that follows pushes the branch and…
update-pr-body
Bring the pull request's description in line with the final change. It was written when the draft opened; the base merge and correction rounds since then may have falsified claims in it, and a validation may have passed red it has to disclose. Your product is an accurate description, nothing else.
settle-threads
The previous round read unresolved review threads on the pull request, and this round's implementer judged each one like a review finding: fixed it, declined it with evidence, or found it needs a decision this run cannot make. Decide which threads are settled and write the reply each one gets. You write nothing…
fix-issue
Fixes GitHub issues using parallel analysis agents for root cause investigation, code exploration, and regression detection. Reads issue context from gh CLI, searches codebase and memory for related patterns, generates a fix with tests, and links the resolution back to the issue via PR. Includes prevention analysis to…