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/Fmarzochi/EGCWrote 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/fmarzochi/egc/pr)<a href="https://agentmods.dev/commands/fmarzochi/egc/pr"><img src="https://agentmods.dev/badge/commands/fmarzochi/egc/pr/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/fmarzochi/egc/pr"><img src="https://agentmods.dev/badge/commands/fmarzochi/egc/pr.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.00021 | $0.01275 |
| Opus 5.5 | $0.00008 | $0.00510 |
| Sonnet 5.5 | $0.00004 | $0.00255 |
| Haiku 4.5 | $0.00002 | $0.00128 |
Grade A, and why
pr 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.
This is a copy
94% identical to pr — 32 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 185 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create Pull Request
Input: $ARGUMENTS: optional, may contain a base branch name and/or flags (e.g., --draft).
Parse $ARGUMENTS:
- Extract any recognized flags (
--draft) - Treat remaining non-flag text as the base branch name
- Default base branch to
mainif none specified
Phase 1: VALIDATE
Check preconditions:
git branch --show-current
git status --short
git log origin/<base>..HEAD --oneline
| Check | Condition | Action if Failed |
|---|---|---|
| Not on base branch | Current branch ≠ base | Stop: "Switch to a feature branch first." |
| Clean working directory | No uncommitted changes | Warn: "You have uncommitted changes. Commit or stash first." |
| Has commits ahead | git log origin/<base>..HEAD not empty |
Stop: "No commits ahead of <base>. Nothing to PR." |
| No existing PR | gh pr list --head <branch> --json number is empty |
Stop: "PR already exists: #. Use gh pr view <number> --web to open it." |
If all checks pass, proceed.
Phase 2: DISCOVER
PR Template
Search for PR template in order:
.github/PULL_REQUEST_TEMPLATE/directory: if exists, list files and let user choose (or usedefault.md).github/PULL_REQUEST_TEMPLATE.md.github/pull_request_template.mddocs/pull_request_template.md
If found, read it and use its structure for the PR body.
Commit Analysis
git log origin/<base>..HEAD --format="%h %s" --reverse
Analyze commits to determine:
- PR title: Use conventional commit format with type prefix:
feat: ...,fix: ..., etc.- If multiple types, use the dominant one
- If single commit, use its message as-is
- Change summary: Group commits by type/area
File Analysis
git diff origin/<base>..HEAD --stat
git diff origin/<base>..HEAD --name-only
Categorize changed files: source, tests, docs, config, migrations.
Planning Artifacts
Check for related artifacts produced by /plan-prd, /plan, or the legacy PRP workflow:
.Gemini/prds/: PRDs this PR implements a milestone of.Gemini/plans/: Plans executed by this PR.Gemini/PRPs/prds/: legacy PRP PRDs.Gemini/PRPs/plans/: legacy PRP implementation plans.Gemini/PRPs/reports/: legacy PRP implementation reports
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 · 185 lines · 21 tokens per session scan A f72779d103d0
pr is a command published in the GitHub repository Fmarzochi/EGC (67 stars, last pushed today), licensed Apache-2.0. It adds 21 tokens to every session and 1,275 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 94% identical to pr, differing in 32 lines, and is treated as a copy.
Other commands, from other repositories
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…
get-unpublished-changes
Compare HEAD with the latest published npm versions and list all unpublished changes by release layer.
release
Release manager for frontend and mobile. Writes App Store notes, user-facing changelog, flags stale docs and landing copy. Actions: notes | changelog | docs | sync.
sweep-mode-c-lifecycle
If Mode C was selected, the wave lifecycle is the back half of the issue-side lifecycle: no Curator, no Approval gate, no Builder. Each PR is routed by its current label to Judge, Doctor→Judge, or Merge directly.
release-tag
Create and push a version tag after a release PR has been merged.
review-code
Read ALL memory bank code rules + best practices, check the files that changed, and APPLY fixes so they adhere. The active counterpart to /scan (which is read-only). Use after an AI session, before commit, to make changed files compliant.