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.
npx agentmods add rules/hatefsystems/search-engine-core/logging-debuggit clone --depth 1 https://github.com/hatefsystems/search-engine-coreWhat 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 | $0.00281 | $0.00281 |
| Opus 5 | $0.00140 | $0.00140 |
| Sonnet 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 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.
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.
- yesterday 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 28d ago), licensed Apache-2.0. It adds 281 tokens to every session, about $0.0014 per session on Opus 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
documentation
Documentation module guidelines for Infinispan docs.
infinispan
Infinispan project guidelines for coding and reviews.
cli
CLI module specific guidelines.
query
Query module specific guidelines.
agents
../../AGENTS.md.
qb-linq-headers
qb-linq implementation headers — CRTP, out-of-line locations, safe patterns.