What is search-engine-core frontend.instructions.md?

A set of project rules for the frontend, covering templates, translations, stylesheets, scripts, and internal links. Localization means adapting the interface for different languages.

Use it when changing templates, adding translations, writing CSS or JavaScript, or creating links in the web interface.

It prevents inconsistent file placement, broken language fallbacks, unsafe browser event code, and links that fail outside local development.

search-engine-core frontend.instructions.md — Instructions file by hatefsystems

Install

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.

agentmods

npx agentmods add instructions/hatefsystems/search-engine-core/frontend

Clone the repo

git clone --depth 1 https://github.com/hatefsystems/search-engine-core

Made for: GitHub Copilot.

Per session 361 This file is loaded in full into every session.

When invoked 361 The same file — it is already loaded in full.

Security scan A 0 findings. Scan, not verified.

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.

Model	Per session	Once invoked
Fable 5	$0.00361	$0.00361
Opus 5	$0.00180	$0.00180
Sonnet 5	$0.00072	$0.00072
Haiku 4.5	$0.00036	$0.00036

Measured yesterday against content hash 5cb0ac8b9dcd, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

search-engine-core frontend.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 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.

.github/instructions/frontend.instructions.md · 49 lines

What it actually says

Frontend Integration

Paths

Static: /public/ (StaticFileController, 1-year cache for JS/CSS)
Templates: /templates/ (Inja)
Locales: /locales/ — use language subfolders (en/, fa/), not files in root. Keep languages.json in root.

Localization Loading

// Load from language-specific folder
std::string localesPath = "locales/" + lang + "/crawling-notification.json";
std::string localeContent = loadFile(localesPath);
if (localeContent.empty()) {
    localesPath = "locales/en/crawling-notification.json";
    localeContent = loadFile(localesPath);
}

Locales checklist: locales/en/, locales/fa/; descriptive filenames (common.json, sponsor.json); fallback to English.

Links

Use {{ base_url }} for all internal links. Never hardcode localhost or port.

<a href="{{ base_url }}/crawl-request">Crawl Request</a>

CSS

Reuse existing classes; define shared values in :root; use BEM and utility classes.

JavaScript (CSP)

No inline handlers (onclick, etc.). Use data-* attributes and addEventListener().

<button data-copy-text="text" class="copy-btn">Copy</button>

Use addEventListener() and event delegation for dynamic elements. No onclick, onload, onsubmit, etc. in HTML.

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.

yesterday First seen · 49 lines · 361 tokens per session scan A 5cb0ac8b9dcd

Subscribe to this mod's changes

search-engine-core frontend.instructions.md is an instructions file published in the GitHub repository hatefsystems/search-engine-core (5 stars, last pushed 28d ago), licensed Apache-2.0. It adds 361 tokens to every session, about $0.0018 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.

Frontend Localization Writing and docs c-plus-plus hatef search-engine

Xapiand AGENTS.md

Instructions for Kronuz/Xapiand, covering agents.md — working in the xapiand codebase, first, the big split: own code vs. vendored, where things live, build & toggles and verifying changes end-to-end (the docs are a test suite).

Kronuz/Xapiand · 2,843 tokens

recharts AGENTS.md

Instructions for recharts/recharts: This is Recharts repository. Recharts is a React-based charting library. The goal is to provide a simple, declarative, and composable way to build charts. We value consistency, usability, and performance. Accessibility is important.

recharts/recharts · 310 tokens

search-engine-core frontend.instructions.md