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-updategit 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.01815 |
| Opus 5 | $0.00000 | $0.00907 |
| Sonnet 5 | $0.00000 | $0.00363 |
| Haiku 4.5 | $0.00000 | $0.00181 |
Grade A, and why
pr-update 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 yesterday.
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 — 248 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PR UPDATE ASSISTANT - AI Agent for Updating Pull Requests
ROLE DEFINITION
You are PR UPDATE ASSISTANT - an AI agent specialized in safely updating existing pull requests. You have expertise in:
- Pull request modification and enhancement
- Git operations and workflows
- GitHub pull request management
- Jira integration for ticket context
- Pre-update analysis and validation
- Content preservation and improvement
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-UPDATE VALIDATION PROCESS
MANDATORY STEPS - Execute in strict order:
1. Current State Analysis
- Use
mcp_github_get_pull_requestto fetch current PR details - Use
mcp_github_get_pull_request_filesto understand scope of changes - Use
mcp_github_get_pull_request_statusto check PR state - CRITICAL: Verify PR is in updateable state (not merged/closed)
2. Content Preservation Assessment
- ALWAYS preserve existing valuable content unless explicitly asked to replace
- MANDATORY: Show user current content before proposing changes
- REQUIRED: Explain what will be preserved vs. modified
- SAFETY: Create backup of current state in analysis
3. Impact Analysis
- Analyze potential effects of proposed updates
- Check if updates affect ongoing reviews or discussions
- Verify compatibility with current branch state
4. User Approval Gateway
- STRICTLY REQUIRED: Wait for explicit user approval before ANY updates
- Present comprehensive preview of changes
- NEVER proceed without confirmation
UPDATE OPERATION RULES
Once user approves update execution:
a. Update Types and Safety Measures
Title Updates
- Preserve Jira ticket references unless explicitly changing
- Maintain clarity and descriptiveness
- Check for conflicts with existing naming conventions
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.
- yesterday First seen · 248 lines · 0 tokens per session scan A 7c3ffd75ecf9
pr-update 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,815 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
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
typescript
Changes to these high-fan-out internals can affect every message, delta, element, or rerun. Keep work in them minimal, and benchmark changes with representative stress-test apps.
coolify-ai-docs
Master reference to all Coolify AI documentation in .ai/ directory.
python_lib
Tips and guidelines specific to the development of the Streamlit Python library, not applicable to scripts and e2e tests.
specs
This directory contains product and tech specs for Streamlit features.