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/fumito-ito/mdcvalultWrote 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/rules/fumito-ito/mdcvalult/guidelines-for-creating-pull-requests-of-github)<a href="https://agentmods.dev/rules/fumito-ito/mdcvalult/guidelines-for-creating-pull-requests-of-github"><img src="https://agentmods.dev/badge/rules/fumito-ito/mdcvalult/guidelines-for-creating-pull-requests-of-github.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.00010 | $0.00448 |
| Opus 5 | $0.00005 | $0.00224 |
| Sonnet 5 | $0.00002 | $0.00090 |
| Haiku 4.5 | $0.00001 | $0.00045 |
Grade A, and why
guidelines-for-creating-pull-requests-of-github 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 8d 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.
What it actually says
Basics
- When referencing this file, shout 'CREATE PULL REQUEST!' out loud.
Pull Request Creation Process
Prerequisites
- Check the Issue Number
- If an issue link is not provided, ask the user: "Is there a related issue link?"
- If no related issue exists, explicitly mention this in the PR description.
Reviewing Changes
- Use the following command to check the diff against the target branch:
git diff origin/{{TARGET_BRANCH}}...HEAD | cat - If no specific target branch is given, default to main.
Preparing Links for the Description
- Confirm that the issue link is included (as checked in the prerequisites).
Creating and Viewing the Pull Request
- Use the following command to create a pull request and open it in a browser:
git push origin HEAD && \
gh pr create --draft --title "{{PR_TITLE}}" --body $'{{PR_TEMPLATE_SINGLE_LINE}}' && \
gh pr view --web
- Ensure the PR title and description reflect the diff against the target branch.
- Unless specified otherwise, create the PR as a Draft.
- Convert the PR template into a single-line string using \n for line breaks.
- Utilize $'...' syntax to ensure correct handling of newline characters.
- Clearly separate each section with appropriate heading levels.
- Ensure all necessary information is provided without omissions.
PR Template
## Summary
{{SUMMARY}}
### Related Issues / Documents
- {{ISSUE_LINK}}
*If no related issue exists, explain why.*
### Changes
- {{CHANGES}}
## Areas of Focus for Reviewers
- {{REVIEW_POINTS}}
## Impact Scope
- {{IMPACT_SCOPE}}
## Screenshots
- {{SCREENSHOTS}}
## Steps to Verify
{{VERIFICATION_STEPS}}
Required Sections
- Summary
- Related Issue (if no related issue exists, explain why)
- Changes
Optional Sections
- Areas of Focus for Reviewers
- Impact Scope
- Screenshots
- Steps to Verify
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.
- 8d ago First seen · 78 lines · 10 tokens per session scan A a6ea722a0fa8
guidelines-for-creating-pull-requests-of-github is a cursor rule published in the GitHub repository fumito-ito/mdcvalult (33 stars, last pushed 1y ago), licensed MIT. It adds 10 tokens to every session and 448 once invoked, about $0.0001 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-30.
Other cursor rules, from other repositories
commit.detail
A detailed checklist for making Git commits safely. It covers reviews, automated checks, documentation alignment, staged-file handling, and release-related safeguards.
gitlab-mr-review
Review GitLab merge requests via glab when user says "mr this" or "pr this".
check
Analyze staged git changes with archguardian before committing.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
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.