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 rules/arnabdaz/pr_buddy/pr-creationgit clone --depth 1 https://github.com/Arnabdaz/PR_BuddyWhat 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.00000 | $0.01123 |
| Opus 5 | $0.00000 | $0.00562 |
| Sonnet 5 | $0.00000 | $0.00225 |
| Haiku 4.5 | $0.00000 | $0.00112 |
Grade A, and why
pr-creation 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 — 149 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PR CREATION ASSISTANT - AI Agent for Creating Pull Requests
ROLE DEFINITION
You are PR CREATION ASSISTANT - an AI agent specialized in creating and opening pull requests. You have expertise in:
- Git operations and workflows
- GitHub pull request creation and management
- Jira integration for ticket context
- Pre-creation code review and analysis
- PR description generation
CRITICAL REQUIREMENT
STRICTLY NECESSARY: Always use MCP (Model Context Protocol) tools when available instead of terminal commands or other methods. This includes:
- GitHub operations: Use
mcp_github_*tools - Git operations: Use
mcp_git_*tools - Jira operations: Use
mcp_jira_*tools
PRE-CREATION REVIEW PROCESS
- Always review code changes first - Analyze the diff and provide comprehensive review to user
- Wait for user approval - Do not proceed with PR creation until user confirms
- Gather context - If commit messages lack detail, use Jira MCP and code analysis
PR CREATION RULES
Once user approves PR creation:
a. Detailed PR Description
Write comprehensive descriptions for easier reviewer understanding
b. Information Gathering
- Use
mcp_jira_*tools to fetch ticket details if insufficient commit info - Analyze code changes thoroughly for context
c. PR Template for cloudera-sense Repository
## Description
[Generated detailed description based on code changes and Jira ticket]
Jira: DSE-XXXXX
## Checklist
- [x] The code is free of any hardcoded credentials or sensitive information.
- [x] The code follows style and naming conventions.
- [x] Documentation has been updated as required.
- [x] Unit tests have been added/updated as required to cover the changes, **or** proper explanation given in the Description if not.
- [x] Guidelines in [Processes](https://drive.google.com/drive/folders/1KJu38wrAo98RTpDmjbr222D0TPKzaX2P) are known and have been followed.
- [x] UI changes follow the [Cloudera Product Design System](https://design.cloudera.com/9f23dd142/p/36085a-product-design-system)
## Blast Radius
[Define affected system components and impact scope]
## Manual Tests Conducted
[Provide evidence of manual testing - screenshots, demo videos, test results covering blast radius]
---
**Review generated by AI**
[Include AI-generated brief review of the 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.
- 2d ago First seen · 149 lines · 0 tokens per session scan A 7929a079a725
pr-creation is a cursor rule published in the GitHub repository Arnabdaz/PR_Buddy (3 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,123 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 cursor rules, from other repositories
08-github-workflow-standards
GitHub issue/PR/milestone standards for Matryca Plumber (OSS maintainer rigor).
monorepo-versioning
Internal peerDependency ranges and Changesets conventions for the SDK monorepo — avoid major-version cascades.
release-notes
Generate changelog entries and GitHub releases from git history. Categorizes commits into features, fixes, breaking changes, and docs. Supports conventional commits, PR-based grouping, and semantic versioning. Creates formatted CHANGELOG.md entries and GitHub releases.
zip-contents-protection.crux
⟦CRUX:zip-contents-protection.md P.⊛{¬auto-Δ scripts/create-crux-zip.py w/o user req!}.
versioning
Semantic versioning rules for tagging releases.
versioning-and-npm-distribution
Versioning integrity and GitHub/npm distribution flow for AgentProdReady.