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.
git clone --depth 1 https://github.com/movebrickschi/harness-engineering-mcpWrote 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.
[](https://agentmods.dev/rules/movebrickschi/harness-engineering-mcp/11-observability-logging)<a href="https://agentmods.dev/rules/movebrickschi/harness-engineering-mcp/11-observability-logging"><img src="https://agentmods.dev/badge/rules/movebrickschi/harness-engineering-mcp/11-observability-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.
<a href="https://agentmods.dev/rules/movebrickschi/harness-engineering-mcp/11-observability-logging"><img src="https://agentmods.dev/badge/rules/movebrickschi/harness-engineering-mcp/11-observability-logging.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00328 |
| Opus 5.5 | $0.00000 | $0.00131 |
| Sonnet 5.5 | $0.00000 | $0.00066 |
| Haiku 4.5 | $0.00000 | $0.00033 |
Grade A, and why
11-observability-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.
What it actually says
可观测性与日志规范
结构化日志
使用JSON格式输出，必须包含以下字段：
| 字段 | 说明 |
|---|---|
| trace_id | 链路追踪ID |
| span_id | 跨度ID |
| timestamp | 时间戳 |
| severity | 日志级别 |
| message | 日志消息 |
日志级别规范
| 级别 | 使用场景 |
|---|---|
| ERROR | 需要立即处理的系统错误 |
| WARN | 业务异常、可恢复的错误 |
| INFO | 关键业务路径（登录、支付、状态变更） |
| DEBUG | 开发调试信息，生产环境关闭 |
禁止在日志中打印：密码、Token、信用卡号、身份证号。使用MDC存储用户上下文。
监控埋点
黄金指标（RED/USE）
- Latency：接口响应延迟
- Traffic：请求流量
- Errors：错误率
- Saturation：资源饱和度
业务指标
使用Micrometer + Prometheus暴露端点，关键方法添加@Timed、@Counted注解。
链路追踪
异步方法必须传递Tracing Context，确保链路完整。
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 · 48 lines · 328 tokens per session scan A e90ebc9b0c36
11-observability-logging is a cursor rule published in the GitHub repository movebrickschi/harness-engineering-mcp (2 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 328 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.
Other cursor rules, from other repositories
beanstalk-deploy
Robust deployment patterns for Elastic Beanstalk with GitHub Actions, Pulumi, and edge case handling.
aws-ecs
Definitive guidelines for building, deploying, and operating applications on AWS ECS, emphasizing immutable containers, secure secrets management, and robust operational patterns.
aws-rds-best-practices
AWS RDS PostgreSQL best practices - database configuration, connection management, authentication, backup, and performance optimization standards.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.