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/ivangrynenko/cursorrules/confluence-editing-standardsgit clone --depth 1 https://github.com/ivangrynenko/cursorrulesWhat 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.00377 | $0.00377 |
| Opus 5 | $0.00188 | $0.00188 |
| Sonnet 5 | $0.00075 | $0.00075 |
| Haiku 4.5 | $0.00038 | $0.00038 |
Grade A, and why
confluence-editing-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 2d 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
Confluence Editing Standards (Markdown Authoring)
Purpose: Ensure Markdown renders cleanly in Confluence by applying spacing, nesting, and code formatting rules during page creation/updates.
Lists & Spacing
-
Always insert a blank line between list items.
-
Use nested sub-bullets for subpoints; never concatenate multiple points on a single line.
-
For ordered lists, keep each step single-purpose; add an empty line between steps when a step has sub-bullets.
Inline vs Code Blocks
-
Prefer inline code for short, single-line commands or file paths (e.g.,
composer install). -
Use fenced code blocks only when necessary (multi-line commands, config snippets). Verify Confluence renders the block without collapsing; otherwise, convert to inline steps.
-
Do not mix bullets and code blocks without a blank line before and after the block.
Headings & Anchors
-
Keep headings concise; avoid trailing punctuation.
-
When using Markdown format, avoid enabling heading anchors if they introduce ID artifacts in rendered output.
Tables
-
Keep tables simple (5–7 columns max). Prefer bullets when content wraps heavily.
-
Add a brief sentence above a large table explaining what it captures.
Nested Structure
- Depth guidance: limit nesting to two levels (bullet → sub-bullet). If content requires more depth, split into a new subsection.
Check Before Publish (Quicklist)
-
Bullets have blank lines between items.
-
Sub-bullets are properly indented and grouped.
-
Commands are inline where possible; multi-line blocks tested for rendering.
-
No anchor artifacts in headings.
-
Tables are readable; consider bullets if wide.
Optional Page Label Cue
When editing an existing Confluence page, if the page has label format-spaced-lists, apply these spacing rules strictly even if the original content is inconsistent.
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.
- 2d ago First seen · 46 lines · 377 tokens per session scan A 8d624224279c
confluence-editing-standards is a cursor rule published in the GitHub repository ivangrynenko/cursorrules (88 stars, last pushed 10mo ago), licensed MIT. It adds 377 tokens to every session, about $0.0019 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-30.
Other cursor rules, from other repositories
java
Modern Java: records, sealed classes, streams, virtual threads.
javascript
Modern JavaScript: ES2023+, async patterns, common traps.
accessibility
Accessibility: semantic HTML, ARIA, keyboard navigation, testing.
cross-tool-config
Cross-tool AI config: what transfers between Cursor, Claude Code, Copilot, Windsurf, Gemini, and Codex.
angular
Angular: signals, standalone components, RxJS patterns.
django
Django: models, views, ORM best practices.