search-engine-core: Instructions file for GitHub Copilot

.github/instructions/controllers.instructions.md

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

A set of C++ rules for registering HTTP controllers and creating their services only when first needed. An HTTP controller connects web requests to application code.

In plain words
What is it for?
Use it when adding or changing API controllers, routes, service dependencies, or controller initialization.
Why use it?
It keeps routes registered consistently and avoids startup-order errors caused by constructing services too early.

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 →

Needs its repository: it reads a path above its own folder, which exists only inside the repository. The line is #include "../../include/routing/Controller.h".

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/controllers.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 controllers.instructions.md

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

Your own site · 80×15
<a href="https://agentmods.dev/instructions/hatefsystems/search-engine-core/controllers"><img src="https://agentmods.dev/badge/instructions/hatefsystems/search-engine-core/controllers.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 342 This file is loaded in full into every session.
When invoked 342 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.00342 $0.00342
Opus 5.5 $0.00137 $0.00137
Sonnet 5.5 $0.00068 $0.00068
Haiku 4.5 $0.00034 $0.00034

Measured 2mo ago against content hash c0aadea3d8e6, 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 controllers.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/controllers.instructions.md · 56 lines

What it actually says

Controller Rules

Required Includes

#include "../../include/routing/Controller.h"
#include "../../include/routing/RouteRegistry.h"

No Namespaces

Controllers must NOT use namespaces (breaks ROUTE_CONTROLLER macro). Use global namespace.

Route Registration (in header, after class)

ROUTE_CONTROLLER(MyController) {
    using namespace routing;
    REGISTER_ROUTE(HttpMethod::GET, "/api/v2/my-endpoint", myEndpoint, MyController);
    REGISTER_ROUTE(HttpMethod::POST, "/api/v2/another-endpoint", anotherEndpoint, MyController);
}
  • No separate *_routes.cpp files. No namespaces around controller class.

Lazy Initialization

Never initialize services in the controller constructor (static initialization order fiasco).

// ✅ CORRECT - with error handling
mutable std::unique_ptr<DomainStorage> domainStorage_;
DomainStorage* getDomainStorage() const {
    if (!domainStorage_) {
        try {
            LOG_INFO("Lazy initializing DomainStorage");
            domainStorage_ = std::make_unique<DomainStorage>();
        } catch (const std::exception& e) {
            LOG_ERROR("Failed to lazy initialize DomainStorage: " + std::string(e.what()));
            throw;
        }
    }
    return domainStorage_.get();
}
  • Declare as mutable std::unique_ptr<Service>
  • Use getter methods with null check and create on first use
  • Add try-catch and logging in getters
  • Use getter methods instead of direct member access
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 · 56 lines · 342 tokens per session scan A c0aadea3d8e6

Subscribe to this mod's changes

search-engine-core controllers.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 342 tokens to every session, about $0.0014 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 controllers.instructions.md compared with instructions from other repositories

search-engine-core controllers.instructions.md next to 6 instructions from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
search-engine-core controllers.instructions.mdhatefsystems/search-engine-coreInstructions file5yesterdayApache-2.0A342GitHub 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