debugging

A set of bug-fixing rules that requires a failing feedback check before forming theories and a regression test with every fix. A regression test checks that a previously fixed problem does not return.

In plain words
What is it for?
Use it when diagnosing or fixing bugs, failed checks, and regressions.
Why use it?
It makes failures easier to reproduce and helps prevent the same bug from coming back.

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/bettertyped/hype-stack/debugging
Clone the repo
git clone --depth 1 https://github.com/BetterTyped/hype-stack

Made for: Cursor.

Per session 36 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 313 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. Scan, not verified.
Origin unknown 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.00036 $0.00313
Opus 5 $0.00018 $0.00156
Sonnet 5 $0.00007 $0.00063
Haiku 4.5 $0.00004 $0.00031

Measured yesterday against content hash 7b587d3b8d42, 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 1 finding 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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

- If a test can't reach it, a script or curl invocation with a known-bad output counts — but name the command and run it red at least once before touching the fix.
.cursor/rules/debugging.mdc · 26 lines

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.

Read it on GitHub

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 · 26 lines · 36 tokens per session scan A 7b587d3b8d42

Subscribe to this mod's changes

debugging is a cursor rule published in the GitHub repository BetterTyped/hype-stack (4 stars, last pushed yesterday), with no licence file. It adds 36 tokens to every session and 313 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.