pull-request

A pull-request creation workflow for the current feature branch. A pull request is a request to review and merge branch changes into the project’s main line.

In plain words
What is it for?
Use it to create a GitHub pull request after checking that the branch has changes and is not main or master.
Why use it?
It ensures the proposed title and description come from the actual diff and prevents a pull request from being opened from the default branch.

Agent

Install

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.

agentmods
npx agentmods add agents/davidvujic/my-eca-config/pull-request
Clone the repo
git clone --depth 1 https://github.com/DavidVujic/my-eca-config
Per session 10 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 372 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00010 $0.00372
Opus 5 $0.00005 $0.00186
Sonnet 5 $0.00002 $0.00074
Haiku 4.5 $0.00001 $0.00037

Measured 2d ago against content hash 683dbebb330f, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

pull-request 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.

agents/pull-request.md · 58 lines

What it actually says

Pull request playbook

Use this playbook whenever the user asks for a code review (diff/PR/repo review).

Create Pull Request instructions

Use the gh CLI and the gh pr create command to create a pull request.

CODE CHANGES CONTEXT:

Before creating a pull request, load and execute the git-changes-context skill to obtain diff_context.

If the skill returns: {"error":"NO_DIFF_FOUND"}

Then output: {"status":"no_changes"} and stop. Do not create a pull request.

All title and description content MUST be derived from this diff.

PR CONTENT GENERATION:

After obtaining diff_context, invoke the changes-summary subagent and use its output as the PR description.

The PR title must be derived from that same summary and formatted as a Conventional Commit: (optional-scope):

Choose the type based on the primary intent of the change:

  • feat: new behavior
  • fix: bug fix
  • refactor: internal change without behavior change
  • perf: performance improvement
  • test: tests only
  • docs: documentation only
  • chore: maintenance/config

BRANCH REQUIREMENT:

Do not create a pull request from the default branch (main or master). If the current branch is main or master, stop and report: {"error":"refusing_to_pr_from_default_branch"}

PR DESCRIPTION RULES:

The PR body must be EXACTLY the output from the changes-summary subagent, followed by the required footer below.

Do not add headings. Do not add explanations. Do not add attribution. Do not add file lists. Do not describe the tool usage.

Changes

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.

  1. 2d ago First seen · 58 lines · 10 tokens per session scan A 683dbebb330f

Subscribe to this mod's changes

pull-request is an agent published in the GitHub repository DavidVujic/my-eca-config (11 stars, last pushed 5d ago), licensed MIT. It adds 10 tokens to every session and 372 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-08-30.