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/HoangYell/markdy-comWrote 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/hoangyell/markdy-com/markdy-syntax)<a href="https://agentmods.dev/rules/hoangyell/markdy-com/markdy-syntax"><img src="https://agentmods.dev/badge/rules/hoangyell/markdy-com/markdy-syntax/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.
<a href="https://agentmods.dev/rules/hoangyell/markdy-com/markdy-syntax"><img src="https://agentmods.dev/badge/rules/hoangyell/markdy-com/markdy-syntax.svg" alt="Reviewed on agentmods" width="80" 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.00000 | $0.00396 |
| Opus 5.5 | $0.00000 | $0.00158 |
| Sonnet 5.5 | $0.00000 | $0.00079 |
| Haiku 4.5 | $0.00000 | $0.00040 |
Grade A, and why
markdy-syntax 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 1mo 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
MarkdyScript Architecture Syntax Rules
When writing or editing Markdy (.markdy or .mdy) files:
-
Strict 4-Section Flow:
- Section 1:
sceneandlayoutdirectives (layout LR,theme=midnight). - Section 2: Semantic node declarations (
service OrderSvc "Order Service"). - Section 3:
groupdefinitions (group backend "Backend Tier": ServiceA ServiceB). - Section 4:
beatnarrative blocks (beat name "Title":).
- Section 1:
-
Always Quote Multi-Word Labels:
- Correct:
service api "Payment API Gateway" - Incorrect:
service api Payment API Gateway
- Correct:
-
Always End Beats and Groups with Colons:
beat checkout "Step 1":group vpc "Private VPC":
-
Never Use Forward
->for Return Responses:- Always use
<-for responses (e.g.Client <- Gateway "200 OK"). Using->creates graph ranking cycles and breaks the visual DAG layout.
- Always use
-
Always Place Animated Flows & Cues Inside Beats:
- Flows (
->,<-,~>) and cues (show,glow,frame,pulse) must be indented inside abeatblock.
- Flows (
-
Self-Healing MCP Tool:
- When generating or fixing diagrams, use
@markdy/mcp-servertools (diagnose_markdy_syntax,fix_markdy_code) to verify syntax before presenting.
- When generating or fixing diagrams, use
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.
- 1mo ago First seen · 33 lines · 0 tokens per session scan A e6cc9077c313
markdy-syntax is a cursor rule published in the GitHub repository HoangYell/markdy-com (99 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 396 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
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
as-contract-cast-smell
// ❌ WRONG — bypasses the family ContractSerializer seam const contract = JSON.parse(raw) as Contract; const contract = JSON.parse(raw) as Contract .
no-backward-compatibility
Do not add backward-compatibility shims or migration scaffolding.
typescript-security
// NEVER: Hardcoded secrets const apiKey = "sk-proj-xxxxx".
nextjs-typescript-app-cursorrules-prompt-file
Cursor rules for Next.js development with TypeScript integration.
jev-surfaces
Score premiere-pro-mcp file candidates by product surface before reading more than three files.