troubleshooting

troubleshooting is a cursor rule for Cursor from multei/web. It costs 118 tokens per session, scanned A, original, MIT.

A repository rule requiring runtime and setup errors to be recorded in TROUBLESHOOTING.md. New entries include when the error appears, a terminal excerpt, and numbered fixes.

In plain words
What is it for?
Use it whenever an error occurs: check the existing log first, then document a new problem during the same work session.
Why use it?
It keeps solutions to recurring installation, build, development, testing, and deployment failures in one place for the next person.

Cursor rule for Cursor

Written for Cursor: installed under .cursor/. Also seen: mentions AGENTS.md.

Good fit Use it whenever an error occurs: check the existing log first, then document a new problem during the same work session.

Compare 6 cursor rules from other repositories ↓
Install with agentmods
npx agentmods add rules/multei/web/troubleshooting
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.

Clone the repo
git clone --depth 1 https://github.com/multei/web

Made for: Cursor.

Wrote 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.

agentmods badge for troubleshooting

README.md
[![agentmods](https://agentmods.dev/badge/rules/multei/web/troubleshooting/github.svg)](https://agentmods.dev/rules/multei/web/troubleshooting)
Your own site
<a href="https://agentmods.dev/rules/multei/web/troubleshooting"><img src="https://agentmods.dev/badge/rules/multei/web/troubleshooting/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.

agentmods 80×15 button for troubleshooting

Your own site · 80×15
<a href="https://agentmods.dev/rules/multei/web/troubleshooting"><img src="https://agentmods.dev/badge/rules/multei/web/troubleshooting.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 118 This file is loaded in full into every session.
When invoked 118 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00118 $0.00118
Opus 5.5 $0.00047 $0.00047
Sonnet 5.5 $0.00024 $0.00024
Haiku 4.5 $0.00012 $0.00012

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

Security

Grade A, and why

troubleshooting 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/troubleshooting.mdc · 15 lines

What it actually says

Troubleshooting log

Whenever you hit an install, build, develop, test, or deploy error in this repo:

  1. Check TROUBLESHOOTING.md first.
  2. If it is a new error, append a section there in the same style as existing entries (heading, when it appears, terminal excerpt, numbered steps).
  3. Do this in the same session — do not wait to be asked.

See also AGENTS.md.

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 · 15 lines · 118 tokens per session scan A c07e9df5d5e7

Subscribe to this mod's changes

troubleshooting is a cursor rule published in the GitHub repository multei/web (4 stars, last pushed today), licensed MIT. It adds 118 tokens to every session, about $0.0005 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-11-07.

Related

troubleshooting compared with cursor rules from other repositories

troubleshooting next to 6 cursor rules from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
troubleshootingmultei/webCursor rule4todayMITA118Cursor
error-handling-and-validationholtwood/awesome-cursorrules-zhCursor rule24119d agoMITA185Cursor
css-render-blocking-diagnosisadobecom/da-express-miloCursor rule6yesterdayApache-2.0A1,102Cursor
modus-checkbox-value-inversion-react-shortjulianoczkowski/create-trimble-appCursor rule34mo agoMITA228Cursor
javascript-expert-performancedjm204/frankenbeastCursor rule23d agononeA3Cursor
5-bug-findercmnemoi/cursor-rulesCursor rule21y agoMITA6Cursor
optimisation-rulesfxbravo/Cursor_RulesCursor rule311mo agononeA0Cursor