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/sfc-gh-cconner/support-rules-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/sfc-gh-cconner/support-rules-mcp/12-documentation-standards)<a href="https://agentmods.dev/rules/sfc-gh-cconner/support-rules-mcp/12-documentation-standards"><img src="https://agentmods.dev/badge/rules/sfc-gh-cconner/support-rules-mcp/12-documentation-standards.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.01688 | $0.01688 |
| Opus 5 | $0.00844 | $0.00844 |
| Sonnet 5 | $0.00338 | $0.00338 |
| Haiku 4.5 | $0.00169 | $0.00169 |
Grade A, and why
12-documentation-standards 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 7d 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 — 282 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Documentation Standards
PURPOSE: Documentation requirements and knowledge management best practices.
📚 Documentation Requirements
Mandatory Documentation
- README files must include purpose, usage examples, and troubleshooting
- Rules should have clear PURPOSE statements and examples
- Code should have docstrings for public functions
- Technical decisions should be documented
README Structure
Every component should include a comprehensive README with:
# Component Name
## Purpose
Brief description of what this component does
## Usage
Basic usage examples with code snippets
## Installation/Setup
Step-by-step setup instructions
## Configuration
Configuration options and environment variables
## Examples
Practical usage examples
## Troubleshooting
Common issues and their solutions
## Related Rules
Links to relevant rules or documentation
📝 Rule Documentation Standards
Rule File Structure
# Rule Title
**PURPOSE**: One-sentence description of when to use this rule
## Core Concept
High-level explanation of the rule's purpose
## Key Patterns
Main patterns or practices
## Examples
Concrete examples with code
## Common Mistakes
Anti-patterns to avoid
## Related Rules
Cross-references to other rules
PURPOSE Statement
Every rule must start with a clear PURPOSE:
**PURPOSE**: When to use this rule and what it provides- Be specific and actionable
- Focus on the user's goal
Examples in Rules
- Include working code examples
- Use realistic scenarios
- Show both correct and incorrect patterns
- Test examples before committing
📖 Knowledge Management
Rule Organization
- Core Rules: Fundamental patterns used across all work
- Connector Rules: Specific to individual drivers/connectors
- SPCS Rules: Snowpark Container Services specific
- Workflow Rules: End-to-end processes and standards
- Meta Rules: Complete workflows that include multiple rules
Cross-References
## Related Rules
- **GitHub MCP Integration**: See `01-github-mcp.mdc`
- **DPO Mappings**: See `04-dpo-mappings.mdc`
- **Snowflake CLI**: See `06-snowflake-cli.mdc`
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.
- 7d ago First seen · 282 lines · 1,688 tokens per session scan A 9f475e655a68
12-documentation-standards is a cursor rule published in the GitHub repository sfc-gh-cconner/support-rules-mcp (0 stars, last pushed 11mo ago), licensed Apache-2.0. It adds 1,688 tokens to every session, about $0.0084 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
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.
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.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.