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.
npx agentmods add rules/nazruden/mcp-openvision/markdown-autogit clone --depth 1 https://github.com/Nazruden/mcp-openvisionWrote 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/nazruden/mcp-openvision/markdown-auto)<a href="https://agentmods.dev/rules/nazruden/mcp-openvision/markdown-auto"><img src="https://agentmods.dev/badge/rules/nazruden/mcp-openvision/markdown-auto.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 | $0.00000 | $0.00300 |
| Opus 5 | $0.00000 | $0.00150 |
| Sonnet 5 | $0.00000 | $0.00060 |
| Haiku 4.5 | $0.00000 | $0.00030 |
Grade A, and why
markdown-auto 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 4d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- markdown-auto — 100% identical, 0 lines differ
What it actually says
Markdown Documentation Standards
Context
- When creating or modifying any Markdown documentation
- When establishing documentation structure and style
- When including diagrams, code blocks, or special elements in documentation
Critical Rules
- Follow Markdown best practices for formatting
- Maintain clear document structure with proper heading hierarchy
- Use Mermaid UML diagrams for documenting complex sequences or architecture
- Maximum heading depth: 4 levels
- Indent content within XML tags by 2 spaces
- Code Block need to indicate the language properly after the initial 3 backticks
- Keep tables properly aligned
Examples
Section Heading
Content with bold text and italics.
function example(): void {
console.log('Hello, Universe!');
}
| Name | Type | Description |
|---|---|---|
| id | number | Primary key |
| name | string | User's name |
💡 Tip: Helpful suggestion.
function withoutLanguageSpecified() {
}
|No|proper|alignment|And|invalid|table | or | proper | formatting |||||
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.
- 4d ago First seen · 59 lines · 300 tokens per session scan A f5c01c7b060a
markdown-auto is a cursor rule published in the GitHub repository Nazruden/mcp-openvision (16 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 300 tokens. 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
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.
family-instance-domain-actions
Family instance domain action implementation patterns.