search-engine-core: Instructions file for GitHub Copilot

.github/instructions/logging-debug.instructions.md

search-engine-core logging-debug.instructions.md is an instructions file for GitHub Copilot from hatefsystems/search-engine-core. It costs 281 tokens per session, scanned A, original, Apache-2.0.

Rules for writing application messages through logging functions such as LOG_DEBUG, LOG_INFO, and LOG_ERROR instead of printing directly to the console.

In plain words
What is it for?
Use it when adding debug output, operational messages, warnings, errors, or tests for different logging levels.
Why use it?
It makes diagnostic output consistent and lets operators choose how much detail appears through the LOG_LEVEL setting.

Instructions file for GitHub Copilot

Written for GitHub Copilot: a Copilot instructions file.

This is hatefsystems/search-engine-core's own configuration. It tells GitHub Copilot how to work on search-engine-core itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything search-engine-core configures →

Reuse

Borrowing it

Nothing to install: this file belongs to hatefsystems/search-engine-core. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/hatefsystems/search-engine-core/master/.github/instructions/logging-debug.instructions.md
Clone the repo
git clone --depth 1 https://github.com/hatefsystems/search-engine-core

Made for: GitHub Copilot.

Wrote 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.

agentmods badge for search-engine-core logging-debug.instructions.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/hatefsystems/search-engine-core/logging-debug/github.svg)](https://agentmods.dev/instructions/hatefsystems/search-engine-core/logging-debug)
Your own site
<a href="https://agentmods.dev/instructions/hatefsystems/search-engine-core/logging-debug"><img src="https://agentmods.dev/badge/instructions/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.

agentmods 80×15 button for search-engine-core logging-debug.instructions.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/hatefsystems/search-engine-core/logging-debug"><img src="https://agentmods.dev/badge/instructions/hatefsystems/search-engine-core/logging-debug.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 281 This file is loaded in full into every session.
When invoked 281 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.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

Measured 2mo ago against content hash dfbe6fe1d5bd, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

search-engine-core logging-debug.instructions.md 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 2mo 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.

.github/instructions/logging-debug.instructions.md · 40 lines

What it actually says

Logging and Debug Output

  • Use LOG_DEBUG() instead of std::cout for 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
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. 2mo ago First seen · 40 lines · 281 tokens per session scan A dfbe6fe1d5bd

Subscribe to this mod's changes

search-engine-core logging-debug.instructions.md is an instructions file published in the GitHub repository hatefsystems/search-engine-core (5 stars, last pushed yesterday), 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.

Related

search-engine-core logging-debug.instructions.md compared with instructions from other repositories

search-engine-core logging-debug.instructions.md next to 6 instructions from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
search-engine-core logging-debug.instructions.mdhatefsystems/search-engine-coreInstructions file5yesterdayApache-2.0A281GitHub Copilot
vscode buildNext.instructions.mdmicrosoft/vscodeInstructions file195kyesterdayMITA9,719GitHub Copilot
next.js AGENTS.mdvercel/next.jsInstructions file143ktodayMITA7,461Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchainInstructions file149kyesterdayMITA4,680Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscodeInstructions file195kyesterdayMITA5,516GitHub Copilot
vscode copilot-instructions.mdmicrosoft/vscodeInstructions file195kyesterdayMITA3,093GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harnessInstructions file274k2d agoMITA4,313Codex, OpenCode