Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/speraxos/SperaxOS-AI-Agentsnpx agentmods add rules/speraxos/speraxos-ai-agents/logging-systemWrote 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/speraxos/speraxos-ai-agents/logging-system)<a href="https://agentmods.dev/rules/speraxos/speraxos-ai-agents/logging-system"><img src="https://agentmods.dev/badge/rules/speraxos/speraxos-ai-agents/logging-system.svg" alt="Measured on agentmods" 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.00644 |
| Opus 5 | $0.00000 | $0.00322 |
| Sonnet 5 | $0.00000 | $0.00129 |
| Haiku 4.5 | $0.00000 | $0.00064 |
Grade A, and why
logging-system 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 6d 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.
This is a copy
100% identical to logging-system — 2 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Custom Logger System Guide
This project uses a custom logging system located in scripts/utils/logger.ts for consistent, structured output across all scripts.
🚨 Critical Rule
NEVER use console.log, console.warn, console.error directly in any scripts. Always use the custom Logger.
📝 Logger Usage Patterns
Basic Import
import { Logger } from '../utils/logger';
// OR import specific functions
import { info, warn, error, success, start } from '../utils/logger';
Common Logging Methods
Information and Status
Logger.info('处理文件', '文件名或详情');
Logger.success('操作完成', '目标', '详细信息');
Logger.warn('警告信息', '原因或详情');
Logger.error('错误信息', '错误对象或详情');
Process Flow
Logger.start('开始操作', '目标', '详细信息');
Logger.split('分隔线标题', '='); // 创建分隔线
File Operations
Logger.file('read', 'path/to/file.json', 'success');
Logger.file('write', 'path/to/file.json', 'start');
Logger.file('delete', 'path/to/file.json', 'error');
Translation Process
Logger.translate(agentId, '源语言', '目标语言', 'start');
Logger.translate(agentId, '源语言', '目标语言', 'success');
Logger.translate(agentId, '源语言', '目标语言', 'skip');
Logger.translate(agentId, '源语言', '目标语言', 'error');
Progress and Statistics
Logger.progress(current, total, '操作描述');
Logger.stats({
'总文件数': totalCount,
'成功数量': successCount,
'失败数量': failureCount
});
🎨 Logger Features
Colored Output
- Uses
consolawith colored icons and formatting - Different colors for different log levels
- Consistent visual hierarchy
Structured Information
- Progress bars for long operations
- Statistical summaries
- File operation tracking
- Translation workflow logging
Debugging Support
Logger.debug('调试信息', debugData);
📋 Migration from console.*
Old Pattern ❌
console.log('Processing file:', fileName);
console.warn('File not found:', filePath);
console.error('Error occurred:', error);
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.
- 6d ago First seen · 105 lines · 0 tokens per session scan A b540460d0621
logging-system is a cursor rule published in the GitHub repository speraxos/SperaxOS-AI-Agents (7 stars, last pushed 8mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 644 tokens. A static security scan graded it A with 0 findings. It is 100% identical to logging-system, differing in 2 lines, and is treated as a copy.
Other cursor rules, from other repositories
whitebit-net
Conventions for using WhiteBit.Net when working with the WhiteBit cryptocurrency exchange in C#/.NET. Apply when generating code that interacts with WhiteBit APIs.
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.
cli-error-handling
CLI command error handling patterns.
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.