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/RashadAnsari/myagentsWrote 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/rashadansari/myagents/single-commit-pr)<a href="https://agentmods.dev/rules/rashadansari/myagents/single-commit-pr"><img src="https://agentmods.dev/badge/rules/rashadansari/myagents/single-commit-pr/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/rules/rashadansari/myagents/single-commit-pr"><img src="https://agentmods.dev/badge/rules/rashadansari/myagents/single-commit-pr.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.00254 | $0.00254 |
| Opus 5.5 | $0.00102 | $0.00102 |
| Sonnet 5.5 | $0.00051 | $0.00051 |
| Haiku 4.5 | $0.00025 | $0.00025 |
Grade A, and why
single-commit-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 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.
What it actually says
Single-commit pull requests
Every pull request you open has exactly one commit on top of its base branch.
- Before opening a pull request, squash every commit on the branch into one, with a message that describes the whole change:
git fetch origin <base>,git reset --soft "$(git merge-base HEAD origin/<base>)", thengit commit. - After the pull request is open, fold each follow-up change (review fixes, CI fixes) into that commit with
git commit --amend, then push withgit push --force-with-lease. - To bring in the base branch, rebase onto it (
git rebase origin/<base>) instead of merging it, so no merge commit is added. - Rewrite only branches you created for the pull request. Never force-push the base branch or a branch someone else has pushed to. On those, add a normal commit and tell the user why the pull request has more than one.
- This rule takes precedence over any instruction to add follow-up commits or merge the base branch into a pull request branch you created.
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 · 15 lines · 254 tokens per session scan A 1aee0acf29e1
single-commit-pr is a cursor rule published in the GitHub repository RashadAnsari/myagents (6 stars, last pushed 3d ago), licensed MIT. It adds 254 tokens to every session, about $0.0010 per session on Opus 5.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-10-21.
Other cursor rules, from other repositories
no-cursor-attribution
Git commits must not include Cursor co-author attribution.
manage-scope-iteratively
Implement features incrementally with checkpoints; don't code for 2 hours then show work.
git-conventional-commit-messages
Cursor rules for Git development with conventional commit messages integration.
python-github-setup-cursorrules-prompt-file
Cursor rules for Python development with GitHub setup integration.
commit-message-generation-rule
Rules for writing consistent Git commit messages, using labels such as feat for a feature, fix for a bug, and docs for documentation. A commit message records one set of code changes.
windsurfrules
Pare wraps CLI tools in MCP servers returning structured JSON. Always prefer Pare MCP tools over raw CLI.