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/fmarzochi/egc/prp-prgit 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/prp-pr)<a href="https://agentmods.dev/commands/fmarzochi/egc/prp-pr"><img src="https://agentmods.dev/badge/commands/fmarzochi/egc/prp-pr.svg" alt="Measured on agentmods" 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.00677 |
| Opus 5 | $0.00010 | $0.00338 |
| Sonnet 5 | $0.00004 | $0.00135 |
| Haiku 4.5 | $0.00002 | $0.00068 |
Grade A, and why
prp-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 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 — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pull Request Creator
Input: $ARGUMENTS: optional base branch name and/or flags (e.g., --draft).
Open a pull request whose description a reviewer can trust: assembled from the actual commits and diff, with verification evidence, never from memory of the conversation.
Step 1: Preflight
All four must hold before anything is pushed:
| Check | Command | On failure |
|---|---|---|
| Not on the base branch | git branch --show-current |
Offer to create a feature branch from the current state |
| Base branch exists | git rev-parse --verify {base} |
Ask for the correct base |
| There are commits to propose | git log {base}..HEAD --oneline |
Stop: nothing to open a PR for |
gh is authenticated |
gh auth status |
Stop with the login instruction |
Base branch: first word of $ARGUMENTS if present, otherwise main.
Step 2: Understand the change
Build the PR narrative from evidence:
git log {base}..HEAD --format='%h %s%n%b'
git diff {base}...HEAD --stat
Identify: the user-visible outcome, the commits that carry it, breaking changes, and anything a reviewer will ask about (large diffs, deleted files, dependency changes).
Step 3: Template discovery
Look for a PR template, in order:
.github/PULL_REQUEST_TEMPLATE.md
.github/pull_request_template.md
.github/PULL_REQUEST_TEMPLATE/*.md
docs/pull_request_template.md
When one exists, fill its sections faithfully; empty template sections are deleted, not left as placeholder text. When none exists, use:
## What
{the change, stated as its user-visible outcome}
## Why
{the problem or request behind it}
## Verification
{commands run and their results; screenshots for UI changes}
## Notes for review
{breaking changes, migration steps, or "none"}
Step 4: Push and open
git push -u origin {current-branch}
gh pr create --base {base} --title "{conventional-commit style title}" --body "{assembled body}"
Add --draft when the flag was passed. The PR title follows the same conventional format as commit messages.
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 · 89 lines · 21 tokens per session scan A 93ec3f915a37
prp-pr is a command published in the GitHub repository Fmarzochi/EGC (48 stars, last pushed today), licensed Apache-2.0. It adds 21 tokens to every session and 677 once invoked, about $0.0001 per session on Opus 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-09-03.
Other commands, from other repositories
build
Implement tasks incrementally — build, test, verify, commit. Add "auto" to run the whole plan in one approved pass.
commit
Auto-stage, review, and commit all changes with a conventional commit message.
commit
Create a conventional commit/s from current changes.
commit
Create one conventional commit from an already-scoped change; never push.
pr-package
Prepare a clean delivery package for GitHub from the real git diff vs an explicit base branch, persisted as PRPACKAGE.md (or PRPACKAGE. .md for multi-repo tasks). Produces branch name, commit messages, fetch, checkout, add, commit, and push commands, PR title and body, and reviewer attention points; never invents work…
commit
Commit on a new branch with conventional message.