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/rjmurillo/ai-agents/push-prgit clone --depth 1 https://github.com/rjmurillo/ai-agentsWrote 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/rjmurillo/ai-agents/push-pr)<a href="https://agentmods.dev/commands/rjmurillo/ai-agents/push-pr"><img src="https://agentmods.dev/badge/commands/rjmurillo/ai-agents/push-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 | $0.00008 | $0.00943 |
| Opus 5 | $0.00004 | $0.00472 |
| Sonnet 5 | $0.00002 | $0.00189 |
| Haiku 4.5 | $0.00001 | $0.00094 |
Grade A, and why
push-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 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 — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Push PR Command
Context
- Current git status: !
git status - Current git diff (staged and unstaged changes): !
git diff HEAD - Current branch: !
git branch --show-current
Your task
Based on the above changes:
-
Create a new branch if on main
- Determine the type of change that maps to conventional commit type followed by a 3-5 word description (e.g., fix/parser-log-enrichment)
-
Push the branch to origin
-
Read @.github/PULL_REQUEST_TEMPLATE.md
-
Run the secure path allocator:
python3 -I "${COPILOT_PLUGIN_ROOT:-${CLAUDE_PLUGIN_ROOT:-.claude}}/skills/github/scripts/pr/new_pr.py" --prepare-body-file- Copy the returned path exactly. Do not store it in a shell variable because each tool call runs in a fresh shell.
- Use the Edit tool to replace
<!-- replace with PR body -->in that exact file with the adapted template. - Fill in all sections with actual change information from git diff
- Replace placeholder comments with substantive content
- Check appropriate Type of Change boxes based on actual changes
- List specific files changed, test coverage added, security impacts
- Do NOT leave template comments like
<!-- Brief description -->unfilled - Do NOT copy the template verbatim - adapt every section to your changes
- Include an
## Acceptance criteriaheading with- [ ]or* [ ]bullets. The Validate Spec Coverage job reads these from the PR body, not the linked issue. Any unchecked box makes the signal report FAIL, and that FAIL does not block the merge, so check a box only once the criterion is actually met. Numbered criteria are not recognized.
-
Create a pull request using the new_pr skill script:
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 · 68 lines · 8 tokens per session scan A 9383f9915870
push-pr is a command published in the GitHub repository rjmurillo/ai-agents (45 stars, last pushed today), licensed MIT. It adds 8 tokens to every session and 943 once invoked, about $0.0000 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-08-30.
Other commands, from other repositories
load-session
Load a synced session summary for context.
statusline
Configure which sections appear in the Claude Code statusline.
01_confirm
Extract plan from conversation, create file in draft/, auto-apply non-BLOCKING improvements, move to pending.
02_execute
Execute a plan (auto-moves pending to in-progress) with Ralph Loop TDD pattern.
add-integration
Add support for a new service (like Slack, Notion, or GitHub) with full OAuth and API integration.
update-model-rubric
Research the current LLM landscape and update Carmenta's model routing rubrics with latest models, capabilities, and pricing.