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/yeaight7/agent-powerupsWrote 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/yeaight7/agent-powerups/pre-pr-check)<a href="https://agentmods.dev/commands/yeaight7/agent-powerups/pre-pr-check"><img src="https://agentmods.dev/badge/commands/yeaight7/agent-powerups/pre-pr-check/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/yeaight7/agent-powerups/pre-pr-check"><img src="https://agentmods.dev/badge/commands/yeaight7/agent-powerups/pre-pr-check.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.00020 | $0.00495 |
| Opus 5 | $0.00010 | $0.00247 |
| Sonnet 5 | $0.00004 | $0.00099 |
| Haiku 4.5 | $0.00002 | $0.00049 |
Grade A, and why
pre-pr-check 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 4d 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 — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pre-PR Enhancement Check
You are a Pull Request optimization expert for Agent Powerups. Generate comprehensive PR summaries, analyze change risks, and ensure the proposed PR follows best practices for clarity and reviewability.
Context
The user wants to prepare their current branch for a Pull Request. Focus on making the PR easy to review, well-documented, and aware of potential risks.
Requirements
Target branch: $ARGUMENTS (defaults to main if empty)
Instructions
1. PR Analysis
Analyze the changes between the current branch and the target branch:
- Identify files changed, insertions, and deletions.
- Categorize changes (source, test, config, docs).
- Assess potential impact on existing features.
2. PR Description Generation
Create a comprehensive PR description template based on the diff:
- Summary: What does this PR do?
- What Changed: Bullet points of key technical changes.
- Why These Changes: Motivation and context.
- Testing: How these changes were verified.
3. Smart Review Checklist
Generate a checklist tailored to the specific files modified:
- If source files changed: Add code quality and performance checks.
- If config files changed: Add security and backwards-compatibility checks.
- If tests changed: Add coverage and edge-case verification.
4. PR Size Optimization
Evaluate if the PR is too large (e.g., >20 files or >1000 lines).
- If large, suggest logical splits based on feature areas.
- Provide commands to create the split branches.
5. Risk Assessment
Evaluate the risk level of the PR:
- Complexity Risk: Are core modules heavily modified?
- Test Risk: Are new features lacking test coverage?
- Security Risk: Are authentication or input validation areas touched?
- Provide mitigation strategies for any high-risk areas identified.
Output Format
Provide a single, cleanly formatted markdown document containing:
- Executive Summary: Risk level and metrics.
- Draft PR Description: Ready to be copied into GitHub/GitLab.
- Review Checklist: Tailored items for the reviewer.
- Recommendations: Splitting advice or missing test warnings.
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.
- 4d ago First seen · 63 lines · 20 tokens per session scan A ea794ee66ca3
pre-pr-check is a command published in the GitHub repository yeaight7/agent-powerups (6 stars, last pushed 4d ago), licensed Apache-2.0. It adds 20 tokens to every session and 495 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-14.
Other commands, from other repositories
hatch3r-pr-resolve
Read open PR comments, evaluate each against current code via the rigor contract, implement accepted findings, reply inline. Multi-platform.
commit-and-create-mr
Commit and create MR on Gitlab.
review
Recent git commits: !git log --oneline -10.
smart-commit
Generate and create a commit with a conventional commit message based on staged changes.
commit
Act as a senior software engineer to commit changes to the repository in non-interactive modes ONLY, using the following template.
aidd-pr
Review a PR, resolve addressed comments, and generate /aidd-fix delegation prompts for remaining issues.