A set of rules and utilities for recording application events in both browser-side and server-side code, with exact file locations.

It helps developers add or update logs across client and server code while following the project's file structure.

It reduces inconsistency about how logging is added and where related files belong.

logging — Cursor rule for Cursor by jaycewalzer1/SilverKey-Inc.

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.

README.md

[![agentmods](https://agentmods.dev/badge/rules/jaycewalzer1/silverkey-inc./logging/github.svg)](https://agentmods.dev/rules/jaycewalzer1/silverkey-inc./logging)

Your own site

<a href="https://agentmods.dev/rules/jaycewalzer1/silverkey-inc./logging"><img src="https://agentmods.dev/badge/rules/jaycewalzer1/silverkey-inc./logging/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.

Your own site · 80×15

<a href="https://agentmods.dev/rules/jaycewalzer1/silverkey-inc./logging"><img src="https://agentmods.dev/badge/rules/jaycewalzer1/silverkey-inc./logging.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 503 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.

Model	Per session	Once invoked
Fable 5.1	$0.00000	$0.00503
Opus 5.5	$0.00000	$0.00201
Sonnet 5.5	$0.00000	$0.00101
Haiku 4.5	$0.00000	$0.00050

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

Security

Grade A, and why

logging 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/shared/logging.mdc · 40 lines

What it actually says

Logging utilities

Use centralized logging utilities only.

Required usage

Client code: import logger from Client/packages/logger/ (not raw console.*).
Server code: from logger import log from Server/logger/ (not print, not current_app.logger, not app.utils.security.app_logging — removed).
Stdlib logging is allowed only under Server/logger/bootstrap/ (Flask/Werkzeug levels, third-party noise, tenacity retry hooks via get_infrastructure_logger).
Use dot-notation LogPath strings in log calls: log.info("AUTH", message, data) or log.info("API.POLLING", message, data). Do not pass LOG_CATEGORIES.* or a 4th API_SUBCATEGORIES argument (enforced by silverkey/prefer-log-path).
Always include an appropriate log category and safe contextual metadata.
Keep logs PII-safe; redaction is required for emails, phone numbers, tokens, SSN, and payment identifiers.

Contract updates

When adding a new log category or changing logging configuration contract:

Update scripts/log_contracts/categories.yaml.
Run make log-contracts.
Commit generated logger contract outputs alongside the code change.

Quick checks

rg "console\\.(log|info|warn|error)\\(" Client
rg "\\bprint\\(" Server
make log-contracts-migrate-check — no LOG_CATEGORIES left in log call sites
cd Client && pnpm lint — includes silverkey/prefer-log-path and silverkey/valid-log-path
make log-contracts-lint — legacy category usage + static LogPath allowlist (Client + Server)
python3 Server/scripts/lint/lint_no_stdlib_logging.py — bans import logging, logging.getLogger, current_app.logger, and app_logging under Server/app/
scripts/ci/check-no-app-logging.sh — fails if app_logging is referenced anywhere under Server/

If either query finds new production-path usage, replace with centralized logger APIs.

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.

1mo ago First seen · 40 lines · 0 tokens per session scan A 1ee8f83c8cd7

Subscribe to this mod's changes

logging 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 503 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-09-08.

Debugging

error-handling-and-validation

A code-quality guide for handling errors, invalid inputs, edge cases, preconditions, logging, and user-friendly error messages.

holtwood/awesome-cursorrules-zh · 185 tokens

css-render-blocking-diagnosis

Cursor rule "css-render-blocking-diagnosis" from adobecom/da-express-milo, covering css render-blocking diagnosis & resolution, critical learning from 98 pagespeed achievement, primary diagnostic protocol, step 1: css blocking symptom recognition and step 2: css loading sequence audit.

adobecom/da-express-milo · 1,102 tokens

logging