error-handling

Error-handling rules for a Motia project, including a shared custom error class and a standard error response format.

In plain words
What is it for?
Use them when creating errors, returning failures from APIs, choosing status codes, attaching error codes or metadata, and logging unexpected problems.
Why use it?
They keep expected client errors readable while logging unexpected failures without exposing internal causes.

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/crypticsaiyan/githubwrapped/error-handling
Clone the repo
git clone --depth 1 https://github.com/crypticsaiyan/githubwrapped

Made for: Cursor.

Per session 687 This file is loaded in full into every session.
When invoked 687 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.00687 $0.00687
Opus 5 $0.00344 $0.00344
Sonnet 5 $0.00137 $0.00137
Haiku 4.5 $0.00069 $0.00069

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

Security

Grade A, and why

error-handling 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/architecture/error-handling.mdc · 122 lines

What it actually says

Error Handling Guide

Errors happen, but we need to handle them gracefully. Make sure you create a custom error class for your project, underneath /src/errors/ folder.

Good practices

  • Use Custom error to return errors to the client.
  • Anything that is not the error class, should be logged with logger.error. And root cause should be omitted to the client.

Create a custom Error class

Name: /src/errors/base.error.ts

export class BaseError extends Error {
  public readonly status: number
  public readonly code: string
  public readonly metadata: Record<string, any>

  constructor(
    message: string,
    status: number = 500,
    code: string = 'INTERNAL_SERVER_ERROR',
    metadata: Record<string, any> = {}
  ) {
    super(message)
    this.name = this.constructor.name
    this.status = status
    this.code = code
    this.metadata = metadata

    // Maintains proper stack trace for where our error was thrown
    Error.captureStackTrace(this, this.constructor)
  }

  toJSON() {
    return {
      error: {
        name: this.name,
        message: this.message,
        code: this.code,
        status: this.status,
        ...(Object.keys(this.metadata).length > 0 && { metadata: this.metadata }),
      },
    }
  }
}

Then create sub class for specific errors that are commonly thrown in your project.

Name: /src/errors/not-found.error.ts

import { BaseError } from './base.error'

export class NotFoundError extends BaseError {
  constructor(message: string = 'Not Found', metadata: Record<string, any> = {}) {
    super(message, 404, 'NOT_FOUND', metadata)
  }
}

Core Middleware

Make sure you create a core middleware that will be added to ALL API Steps.

File: /src/middlewares/core.middleware.ts

import { ApiMiddleware } from 'motia'
import { ZodError } from 'zod'
import { BaseError } from '../errors/base.error'

export const coreMiddleware: ApiMiddleware = async (req, ctx, next) => {
  const logger = ctx.logger

  try {
    return await next()
  } catch (error: any) {
    if (error instanceof ZodError) {
      logger.error('Validation error', {
        error,
        stack: error.stack,
        errors: error.errors,
      })

      return {
        status: 400,
        body: {
          error: 'Invalid request body',
          data: error.errors,
        },
      }
    } else if (error instanceof BaseError) {
      logger.error('BaseError', {
        status: error.status,
        code: error.code,
        metadata: error.metadata,
        name: error.name,
        message: error.message,
      })

      return { status: error.status, body: error.toJSON() }
    }

    logger.error('Error while performing request', {
      error,
      body: req.body,
      stack: error.stack,
    })

    return { status: 500, body: { error: 'Internal Server Error' } }
  }
}
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 · 122 lines · 687 tokens per session scan A e8a6bd7a4012

Subscribe to this mod's changes

error-handling is a cursor rule published in the GitHub repository crypticsaiyan/githubwrapped (5 stars, last pushed 8mo ago), licensed MIT. It adds 687 tokens to every session, about $0.0034 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.