logging

A set of rules for writing application logs in a consistent format, using the project’s shared logger and event names.

In plain words
What is it for?
Use it when adding or reviewing logs, naming events, storing trace IDs, or investigating application behavior.
Why use it?
It prevents scattered logging styles, missing event records, and accidental exposure of passwords, tokens, or full message contents.

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/lawofall/agentcore/logging
Clone the repo
git clone --depth 1 https://github.com/Lawofall/AgentCore

Made for: Cursor.

Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 340 The whole file, excluding the scripts and references it only reads on demand.
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.00000 $0.00340
Opus 5 $0.00000 $0.00170
Sonnet 5 $0.00000 $0.00068
Haiku 4.5 $0.00000 $0.00034

Measured yesterday against content hash 82a4367208f7, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, 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 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/logging.mdc · 34 lines

What it actually says

日志规范

How(格式 / 禁止项 / logger API)以本文为准;接缝(trace_id 落库、contextvars)→ 后端架构.md §六·日志。 分析工具与排查方法 → 对话日志分析指南

Logger 获取

from agentcore.core.logging import get_logger
logger = get_logger(__name__)
logger.info("component.action", key=value)

事件命名

格式 组件.动作(snake_case),如 chat.turn_start禁止裸名(无组件前缀)。 事件须登记于 agentcore/observability/catalog.pyscripts/sync_log_event_registry.py);未注册:dev 告警 / prod 放行。

禁止

  • 禁止 logging.getLogger / structlog.get_logger(脱离统一渲染)
  • 禁止记录敏感信息(BYOK key、密码、token)
  • 消息正文只记 preview,不落完整体
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 · 34 lines · 0 tokens per session scan A 82a4367208f7

Subscribe to this mod's changes

logging is a cursor rule published in the GitHub repository Lawofall/AgentCore (78 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 340 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-30.