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/hlalljie/agent-workflow-presets/markdown-formattinggit clone --depth 1 https://github.com/hlalljie/agent-workflow-presetsWrote 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/hlalljie/agent-workflow-presets/markdown-formatting)<a href="https://agentmods.dev/rules/hlalljie/agent-workflow-presets/markdown-formatting"><img src="https://agentmods.dev/badge/rules/hlalljie/agent-workflow-presets/markdown-formatting.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.00210 | $0.00210 |
| Opus 5 | $0.00105 | $0.00105 |
| Sonnet 5 | $0.00042 | $0.00042 |
| Haiku 4.5 | $0.00021 | $0.00021 |
Grade A, and why
markdown-formatting 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 3d 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
User reads markdown in the editor, not preview. Everything must be scannable as raw text.
Do:
- Short paragraphs (2-4 sentences)
- Bullet lists for discrete items
- Numbered lists when order or reference matters
- Bold for key terms inline
- [ ]checkboxes when tracking completion- Blank lines between sections
##/###headers to break up content- Links inline where they naturally fit
Do not:
- Markdown tables — unreadable without preview. Use prose with bold labels or lists. No exceptions.
- Excessive bold/italic
- Deeply nested bullets (2 levels max)
- Long unbroken paragraphs
- Emoji unless asked
- Repeating same info in different formats
- Inline HTML
####or deeper headers — restructure instead- Hard line wraps at 80 chars — let editor handle it
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.
- 3d ago First seen · 28 lines · 210 tokens per session scan A 428f736ec136
markdown-formatting is a cursor rule published in the GitHub repository hlalljie/agent-workflow-presets (2 stars, last pushed 1mo ago), licensed MIT. It adds 210 tokens to every session, about $0.0011 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
cursor
You are working on the checkout service. Preserve transaction integrity and auditability.
frontend-architecture
Vite + React SPA architecture - directory layout, providers, bundle splitting. Tailwind styling in tailwind.mdc.
api-integration
Frontend API Integration Patterns.
general-python-project-rules
General Python project rules for all Python files in the project. Enforces specific Python versions and class usage.
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.