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/hatefsystems/search-engine-coreWrote 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/hatefsystems/search-engine-core/logging-debug)<a href="https://agentmods.dev/rules/hatefsystems/search-engine-core/logging-debug"><img src="https://agentmods.dev/badge/rules/hatefsystems/search-engine-core/logging-debug/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/hatefsystems/search-engine-core/logging-debug"><img src="https://agentmods.dev/badge/rules/hatefsystems/search-engine-core/logging-debug.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.00281 | $0.00281 |
| Opus 5.5 | $0.00112 | $0.00112 |
| Sonnet 5.5 | $0.00056 | $0.00056 |
| Haiku 4.5 | $0.00028 | $0.00028 |
Grade A, and why
logging-debug 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
Logging and Debug Output
- Use
LOG_DEBUG()instead ofstd::coutfor debug messages. - Configure level via
LOG_LEVEL(trace, debug, info, warning, error, none). - Use
LOG_INFO(),LOG_ERROR(),LOG_WARNING()for other levels.
// ❌ WRONG
std::cout << "[DEBUG] Processing " << requestId << std::endl;
// ✅ CORRECT
LOG_DEBUG("Processing request: " + std::to_string(requestId));
Test with LOG_LEVEL=debug and LOG_LEVEL=info to ensure debug is configurable.
LOG_LEVEL Values
| Level | Use Case | What Gets Logged |
|---|---|---|
trace |
Deep debugging | Everything including execution flow |
debug |
Development | WebSocket, crawler, API calls, performance |
info |
Production | Standard operations, system status |
warning |
High-performance | Non-critical issues, performance warnings |
error |
Critical monitoring | System failures, database errors |
none |
Performance testing | No logging output |
Usage
LOG_LEVEL=debug docker-compose up
LOG_LEVEL=info ./server
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 · 281 tokens per session scan A 932d13b16e9f
logging-debug is a cursor rule published in the GitHub repository hatefsystems/search-engine-core (5 stars, last pushed today), licensed Apache-2.0. It adds 281 tokens to every session, about $0.0011 per session on Opus 5.5. 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
error-handling-and-validation
A code-quality guide for handling errors, invalid inputs, edge cases, preconditions, logging, and user-friendly error messages.
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.
modus-checkbox-value-inversion-react-short
Critical bug fix for ModusWcCheckbox value property inversion.
javascript-expert-performance
Profile first. Measure before and after. Never optimize without data.
kiss-ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
5-bug-finder
APPLY WHEN investigating a bug.