platform

Project rules for using the Deno runtime and organizing application logic as registered synchronizations in a `syncs/` folder.

In plain words
What is it for?
Use them when setting up or extending a Deno application that uses synchronizations to coordinate application behavior.
Why use it?
They give the codebase consistent runtime, import, and organization choices so implementation details do not vary between tasks.

Cursor rule for Cursor

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.

agentmods
npx agentmods add rules/eagonmeng/sync-blank/platform
Clone the repo
git clone --depth 1 https://github.com/eagonmeng/sync-blank

Made for: Cursor.

Per session 116 This file is loaded in full into every session.
When invoked 116 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
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 $0.00116 $0.00116
Opus 5 $0.00058 $0.00058
Sonnet 5 $0.00023 $0.00023
Haiku 4.5 $0.00012 $0.00012

Measured yesterday against content hash ac59e27b8b15, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

platform 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 yesterday.

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/platform.mdc · 16 lines

What it actually says

Platform Choices

The following rules establish choices for the runtime, framework, or any additional build steps.

  • Utilize the Deno runtime for simplified tooling and imports. Prefer to use generic imports without version numbers to reliably import libraries.
  • To the greatest extent possible, only implement application logic as synchronizations, and organize them under the syncs/ folder. You may use whatever sub-file/folder structure that helps keep things clear, but remember to register all synchronizations with the same engine.
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. yesterday First seen · 16 lines · 116 tokens per session scan A ac59e27b8b15

Subscribe to this mod's changes

platform is a cursor rule published in the GitHub repository eagonmeng/sync-blank (4 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 116 tokens to every session, about $0.0006 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.