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/wiggitywhitney/mcp-commit-storyWrote 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/wiggitywhitney/mcp-commit-story/clean_code_priority)<a href="https://agentmods.dev/rules/wiggitywhitney/mcp-commit-story/clean_code_priority"><img src="https://agentmods.dev/badge/rules/wiggitywhitney/mcp-commit-story/clean_code_priority/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/wiggitywhitney/mcp-commit-story/clean_code_priority"><img src="https://agentmods.dev/badge/rules/wiggitywhitney/mcp-commit-story/clean_code_priority.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.00474 | $0.00474 |
| Opus 5.5 | $0.00190 | $0.00190 |
| Sonnet 5.5 | $0.00095 | $0.00095 |
| Haiku 4.5 | $0.00047 | $0.00047 |
Grade A, and why
clean_code_priority 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.
What it actually says
Clean Code Over Backwards Compatibility
This project has no external users - prioritize code quality over compatibility.
-
Breaking Changes Are Acceptable
- Refactor freely to improve code structure
- Remove deprecated patterns without transition periods
- Rename functions, classes, and modules for clarity
- Change APIs to be more intuitive or consistent
-
Code Quality Principles
- DRY (Don't Repeat Yourself): Remove duplicate code aggressively
- KISS (Keep It Simple, Stupid): Simplify complex implementations
- Single Responsibility: Split overly complex functions/classes
- Clear Naming: Use descriptive names even if it requires breaking changes
-
Refactoring Guidelines
- Remove dead code immediately rather than deprecating
- Consolidate similar functions into cleaner interfaces
- Extract common patterns into reusable utilities
- Fix import paths and module organization without compatibility layers
-
Examples of Clean Code Priority
# ✅ DO: Clean, direct approach from mcp_commit_story.journal_generate import generate_summary_section # ❌ DON'T: Backwards compatibility shims # Re-export old function names "for compatibility" from mcp_commit_story.journal import old_function_name as generate_summary_section -
When This Rule Applies
- Always - until the project has external users
- During refactoring and code organization
- When fixing import paths and module structure
- When consolidating duplicate functionality
-
When To Reconsider
- Once external users depend on the APIs
- When the project reaches stable release (1.0+)
- If breaking changes would affect documented public interfaces
-
Implementation Strategy
- Make changes in focused commits for easy tracking
- Update all references systematically in the same change
- Remove old patterns completely rather than leaving them
- Prioritize readability and maintainability in all decisions
Remember: Clean, maintainable code is more valuable than compatibility when there are no users to break.
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 · 57 lines · 474 tokens per session scan A 0235cf8463a2
clean_code_priority is a cursor rule published in the GitHub repository wiggitywhitney/mcp-commit-story (15 stars, last pushed 1y ago), licensed MIT. It adds 474 tokens to every session, about $0.0019 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-08-30.
Other cursor rules, from other repositories
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.
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
config-validation-and-normalization
Config validation and normalization responsibilities (defineConfig normalizes, the orm section schema validates and resolves paths, the loader reports per-section diagnostics).