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/floriscornel/todo-mcpWrote 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/floriscornel/todo-mcp/pr-automation)<a href="https://agentmods.dev/rules/floriscornel/todo-mcp/pr-automation"><img src="https://agentmods.dev/badge/rules/floriscornel/todo-mcp/pr-automation/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/floriscornel/todo-mcp/pr-automation"><img src="https://agentmods.dev/badge/rules/floriscornel/todo-mcp/pr-automation.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.00381 | $0.00381 |
| Opus 5 | $0.00191 | $0.00191 |
| Sonnet 5 | $0.00076 | $0.00076 |
| Haiku 4.5 | $0.00038 | $0.00038 |
Grade A, and why
pr-automation 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 9d 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
Pull Request Guidelines
Pre-PR Checklist
When I ask to create a PR, ensure:
-
Code Quality:
-
npm run test:coveragepasses with 80% coverage -
npm run lintpasses without errors -
npm run compilesucceeds -
npm run buildcreates clean distribution
-
-
Commit Structure:
- Commits follow conventional format
- Each commit is focused and atomic
- Commit messages are descriptive
-
Documentation:
- README updated if public API changed
- Code comments for complex logic
- CHANGELOG.md updated for user-facing changes
PR Description Template
Structure PR descriptions for GitHub Copilot review:
## Summary
Brief description of what this PR accomplishes.
## Changes
- [ ] Feature/fix description
- [ ] Any breaking changes
- [ ] Dependencies added/updated
## Testing
- [ ] All tests pass with coverage
- [ ] New tests added for new functionality
- [ ] Manual testing completed
## Review Notes
- Areas that need special attention
- Architecture decisions made
- Trade-offs considered
GitHub Copilot Review Preparation
- Write clear, descriptive PR titles
- Include context about the problem being solved
- Explain non-obvious code decisions
- Tag any breaking changes clearly
- Reference related issues or discussions
Automated Checks
The CI will automatically run:
- Multi-version Node.js testing (18, 20, 22)
- PostgreSQL integration tests
- Code coverage reporting
- Security audit
- Build verification
Don't merge until all CI checks pass.
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.
- 9d ago First seen · 66 lines · 381 tokens per session scan A dcdcbc8204f5
pr-automation is a cursor rule published in the GitHub repository floriscornel/todo-mcp (2 stars, last pushed 6mo ago), licensed MIT. It adds 381 tokens to every session, about $0.0019 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 cursor rules, from other repositories
conventional-commits
Enforce Conventional Commits format for all commit messages.
git-workflow
Vollagentische Entwicklung, Auto-Commits, Commit-Konventionen.
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.
cli-error-handling
CLI command error handling patterns.