no-dividers-in-comments

no-dividers-in-comments is a cursor rule for Cursor from briangmilnes/APAS-VERUS. It costs 107 tokens per session, scanned A, original, MIT.

A code-comment formatting rule that forbids horizontal lines made from dashes, equals signs, or box-drawing characters.

In plain words
What is it for?
Use it when structuring sections inside source-code comments; use plain section titles instead of divider characters.
Why use it?
Decorative divider lines add visual noise and can make comments less consistent.

Cursor rule for Cursor

Written for Cursor: installed under .cursor/.

Good fit Use it when structuring sections inside source-code comments; use plain section titles instead of divider characters.

Compare 6 cursor rules from other repositories ↓
Install with agentmods
npx agentmods add rules/briangmilnes/apas-verus/no-dividers-in-comments
Install

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.

Clone the repo
git clone --depth 1 https://github.com/briangmilnes/APAS-VERUS

Made for: Cursor.

Wrote 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.

agentmods badge for no-dividers-in-comments

README.md
[![agentmods](https://agentmods.dev/badge/rules/briangmilnes/apas-verus/no-dividers-in-comments/github.svg)](https://agentmods.dev/rules/briangmilnes/apas-verus/no-dividers-in-comments)
Your own site
<a href="https://agentmods.dev/rules/briangmilnes/apas-verus/no-dividers-in-comments"><img src="https://agentmods.dev/badge/rules/briangmilnes/apas-verus/no-dividers-in-comments/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.

agentmods 80×15 button for no-dividers-in-comments

Your own site · 80×15
<a href="https://agentmods.dev/rules/briangmilnes/apas-verus/no-dividers-in-comments"><img src="https://agentmods.dev/badge/rules/briangmilnes/apas-verus/no-dividers-in-comments.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 107 This file is loaded in full into every session.
When invoked 107 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00107 $0.00107
Opus 5 $0.00053 $0.00053
Sonnet 5 $0.00021 $0.00021
Haiku 4.5 $0.00011 $0.00011

Measured 7d ago against content hash afda522808fc, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

no-dividers-in-comments 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.

.cursor/rules/style/no-dividers-in-comments.mdc · 22 lines

What it actually says

No Dividers in Comments

Do not use ---, ===, ───, or any other horizontal rule/divider syntax in code comments. No ASCII dividers, no Unicode box-drawing dividers.

Section headers in comments are just words:

// BAD:
// ---
// === Section ===
// ── Section ──────────────────────────────────────────────

// GOOD:
// Section
Changes

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.

  1. 7d ago First seen · 22 lines · 107 tokens per session scan A afda522808fc

Subscribe to this mod's changes

no-dividers-in-comments is a cursor rule published in the GitHub repository briangmilnes/APAS-VERUS (10 stars, last pushed 1mo ago), licensed MIT. It adds 107 tokens to every session, about $0.0005 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-09-03.