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 skills add gullitmiranda/.cursor --skill prgit clone --depth 1 https://github.com/gullitmiranda/.cursorWrote 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/skills/gullitmiranda/.cursor/pr)<a href="https://agentmods.dev/skills/gullitmiranda/.cursor/pr"><img src="https://agentmods.dev/badge/skills/gullitmiranda/.cursor/pr.svg" alt="Measured on agentmods" 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.00039 | $0.03290 |
| Opus 5 | $0.00019 | $0.01645 |
| Sonnet 5 | $0.00008 | $0.00658 |
| Haiku 4.5 | $0.00004 | $0.00329 |
Grade A, and why
pr 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 6d 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 — 515 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pull Request Management
Reference: Linear GitHub Integration - https://linear.app/docs/github#enable-autolink
/pr - Create Pull Request
-
Pre-flight Checks:
- Verify we're on a feature branch (not main/master)
- Check that branch has commits ahead of base branch, if not use the
/commitcommand to commit the changes - Ensure branch is pushed to remote repository
- Confirm GitHub CLI is authenticated
-
Analyze Changes:
- Run
git log main..HEADorgit log master..HEADto see commits - Run
git diff main...HEADto see all changes - Identify primary change type (feat, fix, chore, etc.)
- Determine scope from affected components
- Check for Linear issue references in commits
- Run
-
Generate PR Title:
- Format:
<type>(<scope>): <summary> - Use conventional commit format
- Summarize the overall change, not individual commits
- Keep under 72 characters
- Format:
-
Build PR Description:
- Check for
.github/pull_request_template.md - If template exists, use as base structure
- Generate Summary section from commit messages
- Add Test Plan with checklist items
- Include Linear issue links if mentioned
- Remove template placeholders if no data available
- Check for
-
Create PR:
- Use
gh pr createwith title and body - Use heredoc for proper formatting
- Set base branch (usually main)
- Return PR URL for user as a markdown link
- Use
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.
- 6d ago First seen · 515 lines · 39 tokens per session scan A e1da5681b8bc
pr is a skill published in the GitHub repository gullitmiranda/.cursor (2 stars, last pushed 6mo ago), licensed MIT. It adds 39 tokens to every session and 3,290 once invoked, about $0.0002 per session on Opus 5. 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 skills, from other repositories
review-implement-phase
Implements triaged review actions, commits focused fixes, and posts Done plus resolves threads. Use when the user wants only the implementation phase of the review-framework workflow.
engram-branch-pr
PR creation workflow for Engram following the issue-first enforcement system. Trigger: When creating a pull request, opening a PR, or preparing changes for review.
verify-behavior
Verify or reproduce visible product behavior by driving the real UI with pi-computer-use's checked tools, requiring verified expect postconditions and durable state evidence for meaningful UI flows. Use when triage needs visual reproduction, implementation needs behavioral proof, review needs interactive confirmation…
github-contributor
End-to-end playbook for shipping high-quality pull requests to open-source projects you don't maintain — discovery, CONTRIBUTING compliance, PR-size check, minimal-diff implementation, PR description with AI-assisted disclosure, conflict resolution, and post-submission maintainer interaction. Use whenever creating…
revdiff
Review diffs, files, and documents with inline annotations in a TUI overlay, or answer questions about revdiff usage, configuration, themes, and keybindings. Opens revdiff in agterm/tmux/zellij/herdr/kitty/wezterm/cmux/ghostty/iterm2/emacs-vterm, captures annotations, and addresses them. Works in git, hg, and jj repos…
write-pr
Reference standards for writing pull request titles and descriptions in the tldraw repository, plus the pre-flight comment sweep over the diff. Use as supporting guidance when another skill or workflow needs PR content standards, not as the user-facing create/update PR workflow.