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/zxpmail/ReqForgeWrote 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/zxpmail/reqforge/reqforge-greenkeeper)<a href="https://agentmods.dev/commands/zxpmail/reqforge/reqforge-greenkeeper"><img src="https://agentmods.dev/badge/commands/zxpmail/reqforge/reqforge-greenkeeper/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/zxpmail/reqforge/reqforge-greenkeeper"><img src="https://agentmods.dev/badge/commands/zxpmail/reqforge/reqforge-greenkeeper.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.00010 | $0.00189 |
| Opus 5.5 | $0.00004 | $0.00076 |
| Sonnet 5.5 | $0.00002 | $0.00038 |
| Haiku 4.5 | $0.00001 | $0.00019 |
Grade A, and why
reqforge-greenkeeper 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
Command: /reqforge-greenkeeper
Framework-repo only (ReqForge itself — not a user product built with Forge).
| Phase | Commands | Acceptance |
|---|---|---|
| Baseline | pnpm sync:discover, pnpm test, pnpm forge-smoke |
Failing gate identified |
| Fix | Minimal edit to core source, smoke script, or test | Invariant restored without weakening gates |
| Sync | pnpm sync after core asset edits |
Adapters match core |
| Verify | pnpm sync:discover, pnpm validate-skill core/skills, pnpm test, pnpm forge-smoke |
All green |
Full workflow → SKILL.md + references/workflow.md.
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 · 18 lines · 10 tokens per session scan A 35421a986d0c
reqforge-greenkeeper is a command published in the GitHub repository zxpmail/ReqForge (18 stars, last pushed 12d ago), licensed MIT. It adds 10 tokens to every session and 189 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-30.
Other commands, from other repositories
ijfw-ship
Run the IJFW workflow Ship phase (Deep D6). Pre-flight, deploy, and close. Usage: /ijfw-ship.
pr-package
Prepare a GitHub PR delivery package (branch, commits, PR title and body, reviewer notes) from the real git diff against an explicit base branch, persisted as PRPACKAGE.md, never inventing work outside the diff. Use when scope is done and diff is stable. Do not use mid-implementation, for a branch name (use…
ship
Run the pre-launch checklist via parallel fan-out to specialist personas, then synthesize a go/no-go decision.
get-unpublished-changes
Compare HEAD with the latest published npm versions and list all unpublished changes by release layer.
finish-branch-execute
Step 4 of finishing-a-development-branch: Execute chosen integration option (merge, PR, PR+dance, keep, or discard).
branch-commit
Return a branch name and concise commit message (max 3 lines) for the current task, grounded in the real git diff; with --apply, create the commit after showing the staged diff. Use when the user only needs quick branch and commit naming before committing, PR packaging is unnecessary, and a real diff exists; use…