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/tanchaowen84/GameSiteTemplateWrote 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/tanchaowen84/gamesitetemplate/nextjs-hydration-debugging)<a href="https://agentmods.dev/rules/tanchaowen84/gamesitetemplate/nextjs-hydration-debugging"><img src="https://agentmods.dev/badge/rules/tanchaowen84/gamesitetemplate/nextjs-hydration-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/tanchaowen84/gamesitetemplate/nextjs-hydration-debugging"><img src="https://agentmods.dev/badge/rules/tanchaowen84/gamesitetemplate/nextjs-hydration-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.01242 | $0.01242 |
| Opus 5.5 | $0.00497 | $0.00497 |
| Sonnet 5.5 | $0.00248 | $0.00248 |
| Haiku 4.5 | $0.00124 | $0.00124 |
Grade A, and why
nextjs-hydration-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 2mo 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- 2mo ago First seen · 72 lines · 1,242 tokens per session scan A 694c324ea28f
nextjs-hydration-debugging is a cursor rule published in the GitHub repository tanchaowen84/GameSiteTemplate (9 stars, last pushed 1y ago), with no licence file. It adds 1,242 tokens to every session, about $0.0050 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
mobx-devtools
Instructions for using MobX DevTools, including a browser extension and development component for inspecting application state changes.
mobx-strict-mode
Guidance for enabling MobX strict mode, which requires observable state changes to happen inside actions.
apollo-devtools
A debugging guide for Apollo Client DevTools, a browser extension for inspecting GraphQL requests and Apollo's local cache. It covers queries, mutations, subscriptions, variables, responses, and errors.
browser-diagnosis
Reproducing and diagnosing App Builder in the browser — SDV, Playwright scratch drivers, selection menu pitfalls, PUT counting. Use when debugging UI, selection, or interaction.
debugging
Bug-fixing discipline - build a red feedback loop before hypothesizing, ship every fix with a regression test. Apply whenever diagnosing or fixing a bug, failure, or regression.
dont-do
Things to Avoid - Anti-patterns and Common Mistakes.