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/documentation)<a href="https://agentmods.dev/rules/wiggitywhitney/mcp-commit-story/documentation"><img src="https://agentmods.dev/badge/rules/wiggitywhitney/mcp-commit-story/documentation/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/documentation"><img src="https://agentmods.dev/badge/rules/wiggitywhitney/mcp-commit-story/documentation.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.00545 | $0.00545 |
| Opus 5.5 | $0.00218 | $0.00218 |
| Sonnet 5.5 | $0.00109 | $0.00109 |
| Haiku 4.5 | $0.00055 | $0.00055 |
Grade A, and why
documentation 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.
How it starts
The opening of the file, as written. The whole thing — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Documentation Standards
Core Principle
Write for a future developer with zero project knowledge who needs to understand and modify this system.
Some Possible Elements
- Function-level docstrings for all new functions following the core principle
- Module-level docstrings for new modules explaining their purpose and approach
- Complete examples that are copy-pasteable and work
- Technical context explaining why decisions were made when it affects future changes
- Prerequisites: What they need to install/know first
- Clear steps: How to use, modify, or extend
Documentation Updates for Code Changes
- Evaluate existing documentation before creating new files - determine if new information should be added to existing docs rather than creating separate files
- When code is changed (as opposed to net-new), these must be evaluated and updated if needed:
- Documentation files
- README.md
- Engineering specifications
- PRD (Product Requirements Document)
Forbidden Content
- Process references: No task IDs, sprint numbers, team workflows
- Historical narrative: Skip "we tried X then Y" stories
- Assumed knowledge: No insider team decisions or project history
- Personal references: No names, meetings, or timeline details
- Abstract corporate speak: Use concrete problem descriptions instead
- Meaningless task references: Describe actual accomplishments, not task numbers
Writing Style Requirements
- Specific, concrete language - avoid abstract buzzwords
- Real problem/solution statements - not theoretical concepts
- External reader accessibility - assume no prior project context
- Focus on what's happening - not the development journey
Quality Test
Could a new developer use this documentation successfully without asking questions?
Examples
✅ Good
# Email Service
## Prerequisites
- Node.js 18+, environment vars: `SMTP_HOST`, `SMTP_USER`, `SMTP_PASS`
## Usage
```javascript
import { sendEmail } from './email-service';
await sendEmail('[email protected]', 'Welcome!', template);
Configuration
TIMEOUT=10000: 10s timeout prevents hanging on slow SMTP servers
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 · 69 lines · 545 tokens per session scan A b05f388ffc13
documentation is a cursor rule published in the GitHub repository wiggitywhitney/mcp-commit-story (15 stars, last pushed 1y ago), licensed MIT. It adds 545 tokens to every session, about $0.0022 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).