Borrowing it
Nothing to install: this file belongs to elixpo/claudeOps.elixpo. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/elixpo/claudeOps.elixpo/main/.claude/commands/fill-pr-description.mdgit clone --depth 1 https://github.com/elixpo/claudeOps.elixpoWrote 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/elixpo/claudeops.elixpo/fill-pr-description)<a href="https://agentmods.dev/commands/elixpo/claudeops.elixpo/fill-pr-description"><img src="https://agentmods.dev/badge/commands/elixpo/claudeops.elixpo/fill-pr-description/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/elixpo/claudeops.elixpo/fill-pr-description"><img src="https://agentmods.dev/badge/commands/elixpo/claudeops.elixpo/fill-pr-description.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.00000 | $0.00694 |
| Opus 5 | $0.00000 | $0.00347 |
| Sonnet 5 | $0.00000 | $0.00139 |
| Haiku 4.5 | $0.00000 | $0.00069 |
Grade A, and why
fill-pr-description 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 10d 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 — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Generate a PR description from the diff. Triggered when a whitelisted author puts @elixpoo fill in the PR body.
Inputs (injected into the prompt)
PR_NUMBER— the PRPR_TITLE— current titleAUTHOR— PR author's loginCURRENT_BODY— the existing PR body (contains the@elixpoo filltrigger + optional user blockquotes)DIFF—gh pr diff <n>output, truncated if huge
Procedure
-
Extract user blockquotes from
CURRENT_BODY. Any lines starting with>are notes the author wants preserved verbatim. Keep them as-is. Ignore the@elixpoo filltrigger line itself. -
Summarize the diff into a tight "Changes Made" section:
- One bullet per meaningful file or logical change.
- Reference the file path in backticks and say what changed and why.
- 3-7 bullets. If the diff touches 1 file, 1-2 bullets is fine.
- Skip lockfiles, generated files, and formatting-only noise.
-
Pick the checklist items relevant to this diff. Only include items that actually apply:
- [ ] \export const runtime = 'edge'` on any new API route— only if a newapp/api/**/route.ts` was added.- [ ] No Node built-ins imported (crypto, fs, path, stream, Buffer)— only ifsrc/code changed.- [ ] New DB columns/tables have a migration in \src/workers/migrations/`` — only if D1 / schema changed.- [ ] Rate-limit middleware on new public auth endpoints— only if a newapp/api/auth/**route was added.- [ ] \./biome.sh ci` clean` — always include.- [ ] Tested locally: <how>— always include, leave the "how" unchecked as a prompt for the author.
-
Assemble the final body. Use exactly this structure, keep it tight (no marketing prose):
## Changes Made
- <bullet>
- <bullet>
## Checklist
- [ ] <applicable item>
- [ ] <applicable item>
<user blockquotes here, verbatim, if any>
---
Fixes <linked issue if mentioned in PR title or any commit message; else omit line>
- PATCH the PR body:
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.
- 10d ago First seen · 61 lines · 0 tokens per session scan A d54480817719
fill-pr-description is a command published in the GitHub repository elixpo/claudeOps.elixpo (2 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 694 tokens. 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-31.
Other commands, from other repositories
commit-message
Generate a conventional commit message from staged changes.
commit-push-pr
An automated Git workflow that checks a project, synchronizes documentation, commits changes, and can create or merge a GitHub pull request. A pull request is a request for teammates to review and add changes to a shared codebase.
quick-commit
A quick Git command for committing and pushing a small code change. Git is the tool that records code versions and sends them to a shared repository.
pull-repos
Pull all repos (parent + marketplace clones + configured project repos).
undo-commit
Soft-undo the last commit. Restores its changes as staged, leaves working tree intact. Refuses if HEAD is already pushed to a tracked remote.
changelog
Generate a changelog entry from git commits since the last tag using conventional commit format.