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.
git clone --depth 1 https://github.com/ivangrynenko/cursorrulesWrote 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/ivangrynenko/cursorrules/pr-draft)<a href="https://agentmods.dev/commands/ivangrynenko/cursorrules/pr-draft"><img src="https://agentmods.dev/badge/commands/ivangrynenko/cursorrules/pr-draft/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/ivangrynenko/cursorrules/pr-draft"><img src="https://agentmods.dev/badge/commands/ivangrynenko/cursorrules/pr-draft.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.00736 |
| Opus 5.5 | $0.00000 | $0.00294 |
| Sonnet 5.5 | $0.00000 | $0.00147 |
| Haiku 4.5 | $0.00000 | $0.00074 |
Grade A, and why
pr-draft 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 1mo 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 — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Custom Command: PR Draft
Command Usage
/pr-draft <pr-notes>
The argument <pr-notes> should capture highlights, testing notes, and reviewer callouts. Use it to shape the PR title and body.
You are tasked with creating a pull request (PR) for a code change. Follow these instructions carefully to generate an appropriate PR description and title.
Check if Use the user-provided arguments (if any) as contextual input was provided in a prompt. If not, stop first and ask user for any comments, assign them as Use the user-provided arguments (if any) as contextual input. Process the Use the user-provided arguments (if any) as contextual input, extract the useful information and plan how it might impact pull request creation. If none provided, proceed with the PR creation.
Tool use
Use github cli or github mcp if available for PR creation.
Template
First, here is the PR template that should be used as a base for the pull request description:
<pr_template> the repository pull request template </pr_template>
Now, let's create the pull request:
-
Extract the ticket number: Analyze the branch name provided: the active Git branch name Look for a four-digit number in the branch name, which should represent the Freshdesk ticket number. If found, use it in the next steps. If not found, make a note to ask for it later, unless Use the user-provided arguments (if any) as contextual input instruct you to skip ticket number.
-
Create the PR title: Format: "[#TICKET_NUMBER] [Verb in past tense] [description of the change] [full stop at the end.]" Example: "[#5765] Updated user authentication process."
-
Create the PR description: Start with the PR template provided above.
For the "Freshdesk or JIRA ticket" section:
- If you found a ticket number, add the link: https://servicedesk.salsadigital.com.au/a/tickets/TICKET_NUMBER
- If no ticket number was found, leave a placeholder: "TODO: Add Freshdesk ticket link", However, if you were provided with instructions to skip ticket number, then ignore this line.
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.
- 1mo ago First seen · 63 lines · 0 tokens per session scan A 293af3df1995
pr-draft is a command published in the GitHub repository ivangrynenko/cursorrules (88 stars, last pushed 11mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 736 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
revert
Git-aware undo by logical work unit (track, phase, or task).
matcha:status
🍵 Master session health dashboard — intensity, git diff stats, test status, and marker ledger.
release
Tag a versioned release and push. CI deploys on the tag. The agent does not.
review-pr
Review a GitHub Pull Request end to end. Use when the user shares a GitHub PR URL or PR number and wants the PR prepared locally for review, analyzed using project rules, optionally commented on in GitHub, and optionally synchronized to Jira based on the review outcome.
ready-pr-in-review
Move a PR from Draft to Ready for Review, assign a reviewer, add labels, and sync the related Jira ticket to In Review with the correct assignee.
commit
Git commit command - creates conventional commits.