backend-patterns

backend-patterns is a cursor rule for Cursor from jaycewalzer1/SilverKey-Inc.. It costs 0 tokens per session (1,811 once invoked), scanned A, original, MIT.

A set of rules for common backend code, including routes, request handlers, and examples. Backend code runs on the server rather than in the user's browser.

In plain words
What is it for?
Use it when working on backend routes, handlers, or related implementation examples.
Why use it?
It helps developers follow the project's established structure when adding server-side code.

Cursor rule for Cursor

Written for Cursor: installed under .cursor/.

Good fit Use it when working on backend routes, handlers, or related implementation examples.

Compare 6 cursor rules from other repositories ↓
Install with agentmods
npx agentmods add rules/jaycewalzer1/silverkey-inc./backend-patterns
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/jaycewalzer1/SilverKey-Inc.

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 backend-patterns

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

Your own site · 80×15
<a href="https://agentmods.dev/rules/jaycewalzer1/silverkey-inc./backend-patterns"><img src="https://agentmods.dev/badge/rules/jaycewalzer1/silverkey-inc./backend-patterns.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 1,811 The whole file, excluding the scripts and references it only reads on demand.
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.00000 $0.01811
Opus 5.5 $0.00000 $0.00724
Sonnet 5.5 $0.00000 $0.00362
Haiku 4.5 $0.00000 $0.00181

Measured 1mo ago against content hash 39ce3c08f618, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

backend-patterns 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.

.cursor/rules/backend/backend-patterns.mdc · 322 lines

How it starts

The opening of the file, as written. The whole thing — 322 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Backend Code Patterns Reference

Overview

This document provides code examples and patterns for common backend operations. Use these patterns to ensure consistency across the codebase.

Route Patterns

Standard Protected Route

from flask import Blueprint, request, jsonify
from ..utils.common_patterns import require_authenticated_user, handle_exceptions_with_logging
from ..utils.security.secure_errors import SecureErrorHandler
from app import db

my_bp = Blueprint('my', __name__, url_prefix='/api/v1/my')

@my_bp.route('/resource', methods=['GET'])
@handle_exceptions_with_logging
@require_authenticated_user
def get_resource(user):
    """Get resource for authenticated user"""
    # user is automatically provided by decorator
    resource = get_resource_for_user(user.id)
    from app.dtos.user import UserDTO
    return jsonify({
        'success': True,
        'data': UserDTO.to_response(user),
    })

Agent-Only Route

from ..utils.common_patterns import require_agent_access, handle_exceptions_with_logging

@agent_bp.route('/clients', methods=['GET'])
@handle_exceptions_with_logging
@require_agent_access
def get_clients(user):
    """Get clients for authenticated agent"""
    # user is guaranteed to be an agent
    clients = get_agent_clients(user.id)
    return jsonify({
        'success': True,
        'clients': clients
    })

Route with JSON Validation

from ..utils.common_patterns import validate_json_request, require_authenticated_user

@my_bp.route('/update', methods=['PUT'])
@validate_json_request(required_fields=['name', 'email'])
@require_authenticated_user
def update_profile(user, data):
    """Update user profile - data is automatically validated"""
    user.name = data['name']
    user.email = data['email']
    db.session.commit()
    return jsonify({'success': True})

Combined Decorator Pattern

from ..utils.common_patterns import api_route

@my_bp.route('/resource', methods=['POST'])
@api_route(require_auth=True, require_json=True, required_fields=['field1', 'field2'])
def create_resource(user, data):
    """Create resource with combined decorators"""
    # user and data are automatically provided
    resource = create_resource_for_user(user.id, data)
    from app.dtos.user import UserDTO
    return jsonify({'success': True, 'data': UserDTO.to_response(user)})

Read the full file on GitHub · 322 lines

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. 1mo ago First seen · 322 lines · 0 tokens per session scan A 39ce3c08f618

Subscribe to this mod's changes

backend-patterns is a cursor rule published in the GitHub repository jaycewalzer1/SilverKey-Inc. (2 stars, last pushed 3d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,811 tokens. 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.