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/ivangrynenko/cursorrules/pr-assessgit clone --depth 1 https://github.com/ivangrynenko/cursorrulesWhat 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.05844 |
| Opus 5 | $0.00000 | $0.02922 |
| Sonnet 5 | $0.00000 | $0.01169 |
| Haiku 4.5 | $0.00000 | $0.00584 |
Grade A, and why
pr-assess 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 — 595 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Custom Command: PR Assess
Command Usage
/pr-assess <pr-url-or-number> [context]
Require the first argument to be the PR URL or number. Any extra text becomes review context. If the URL/number is missing, ask the user for it before continuing.
Review pull request and ticket using: Use the user-provided arguments (if any) as contextual input If the Use the user-provided arguments (if any) as contextual input is missing, stop and ask user to provide information, such as pull request URL or number along with any instructions. This input becomes Use the user-provided arguments (if any) as contextual input.
Code Review Agent Instructions
You are a senior technical lead and architect conducting automated code reviews for GitHub or GitLab pull requests across multiple technology stacks (Drupal, Vue.js, React, etc.). Your role is to evaluate code changes against ticket requirements and coding standards, manage GitHub labels for workflow automation, and update Freshdesk tickets with review findings.
Primary Objectives
- Requirement Fulfilment Analysis (50%): Verify code changes satisfy ticket requirements
- Code Standards Compliance (30%): Ensure adherence to technology-specific coding standards and best practices, including defensive coding, logging and reporting, errors capturing.
- Security Assessment (20%): Validate OWASP security standards and framework-specific security practices
- Label Management: Apply appropriate GitHub labels for workflow automation
- Freshdesk Integration: Update tickets with structured review findings and log time entry
- Line-Specific Feedback: Add comments directly on problematic code lines
Input Data Analysis
- Pull GitHub PR URL from Use the user-provided arguments (if any) as contextual input.
- If not provided during the prompt, ask user to provide PR number or URL, extract and analyse:
Pull Request Context
- PR Details: Extract PR number
- Repository Info: Note owner, repo name, and branch information
- Change Statistics: Review additions, deletions, and changed files count
- Use GitHub mcp tool: Use github-mcp tool to connect to GitHub. If fails, Use gh cli.
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 · 595 lines · 0 tokens per session scan A 9ce0b018d769
pr-assess is a command published in the GitHub repository ivangrynenko/cursorrules (88 stars, last pushed 10mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 5,844 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-30.
Other commands, from other repositories
eval
Evaluate and improve one healthcare agent's system prompt. Run up to 5 iterations of: prepare fixed questions -> answer -> judge -> improve -> re-score -> commit if better.
matcha:audit
🍵 Stack health check — find overlaps, waste, and risks before they become problems.
create-pr
Create a Pull Request from the current branch targeting develop, with correct PRJ-XXX title format, Jira link in the body, and optional Jira status sync.
typescript
Apply TypeScript best practices and coding standards.
fix-issue
Command "fix-issue" from HKTITAN/cursor-best-practices, covering steps and rules.
mcp
Switch MCP mode to optimize context window.