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/eagonmeng/sync-blankWrote 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/eagonmeng/sync-blank/debugging)<a href="https://agentmods.dev/rules/eagonmeng/sync-blank/debugging"><img src="https://agentmods.dev/badge/rules/eagonmeng/sync-blank/debugging/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/eagonmeng/sync-blank/debugging"><img src="https://agentmods.dev/badge/rules/eagonmeng/sync-blank/debugging.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.00249 | $0.00249 |
| Opus 5.5 | $0.00100 | $0.00100 |
| Sonnet 5.5 | $0.00050 | $0.00050 |
| Haiku 4.5 | $0.00025 | $0.00025 |
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 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
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.
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 · 29 lines · 249 tokens per session scan A 992a8e975071
debugging is a cursor rule published in the GitHub repository eagonmeng/sync-blank (4 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 249 tokens to every session, about $0.0010 per session on Opus 5.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.
Other cursor rules, from other repositories
error-handling-and-validation
A code-quality guide for handling errors, invalid inputs, edge cases, preconditions, logging, and user-friendly error messages.
css-render-blocking-diagnosis
Cursor rule "css-render-blocking-diagnosis" from adobecom/da-express-milo, covering css render-blocking diagnosis & resolution, critical learning from 98 pagespeed achievement, primary diagnostic protocol, step 1: css blocking symptom recognition and step 2: css loading sequence audit.
modus-checkbox-value-inversion-react-short
Critical bug fix for ModusWcCheckbox value property inversion.
javascript-expert-performance
Profile first. Measure before and after. Never optimize without data.
kiss-ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
5-bug-finder
APPLY WHEN investigating a bug.