debugging

Rules for tracing actions and synchronizations with configurable logs. TRACE summarizes actions and their inputs and outputs, while VERBOSE includes processing details and matched synchronizations.

In plain words
What is it for?
Use them to debug synchronization behavior, inspect record processing, and trace subtle engine or rule problems.
Why use it?
The logs show whether actions and synchronization rules ran as expected, making difficult behavior easier to investigate.

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/debugging
Clone the repo
git clone --depth 1 https://github.com/eagonmeng/sync-blank

Made for: Cursor.

Per session 249 This file is loaded in full into every session.
When invoked 249 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.00249 $0.00249
Opus 5 $0.00125 $0.00125
Sonnet 5 $0.00050 $0.00050
Haiku 4.5 $0.00025 $0.00025

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

Security

Grade A, and why

debugging 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/debugging.mdc · 29 lines

What it actually says

Debugging

The engine contains logging logic to help trace issues, and which action is occuring with what inputs and outputs. After initializing an engine, simply set:

const Sync = new SyncConcept();
Sync.logging = Logging.TRACE; // options are OFF, TRACE, and VERBOSE

TRACE gives a simple summary of every action that happened along with their inputs and outputs, while VERBOSE dives deep and gives a complete account of provenance and the processing of each record, and which synchronizations matched.

In general, the concept design architecture affords reasoning piecemeal about the entire system, meaning that you should be able to test concepts individually, test synchronizations independently, and the frontend on its own. Use output logs from TRACE level logging to find out if actions are occurring as expected or to debug synchronizations (you could build a small script or edit the logging behavior to pipe this information in a better way), and level VERBOSE when absolutely necessary and you might be convinced that there is something wrong with the engine, or a very subtle bug in synchronization formulation.

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 · 29 lines · 249 tokens per session scan A 992a8e975071

Subscribe to this mod's changes

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