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 instructions/hatefsystems/search-engine-core/code-stylegit 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.00352 | $0.00352 |
| Opus 5 | $0.00176 | $0.00176 |
| Sonnet 5 | $0.00070 | $0.00070 |
| Haiku 4.5 | $0.00035 | $0.00035 |
Grade A, and why
search-engine-core code-style.instructions.md scanned grade A with 2 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 2d 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.
Sends data to an external URLlowData exfiltration
A POST to an outside endpoint may be telemetry or may be exfiltration; either way the mod talks to somewhere, and you should know where.
- API: `curl --location 'http://localhost:3000/api/endpoint' --header 'Content-Type: application/json' --data-raw '{ ... }'` Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- API: `curl --location 'http://localhost:3000/api/endpoint' --header 'Content-Type: application/json' --data-raw '{ ... }'` What it actually says
Code Style and Practices
Error Handling
try {
mongocxx::instance& instance = MongoDBInstance::getInstance();
// ...
} catch (const mongocxx::exception& e) {
LOG_ERROR("MongoDB error: " + std::string(e.what()));
serverError(res, "Database error occurred");
}
Includes Order
// System headers first
#include <string>
#include <memory>
// Project headers
#include "../../include/Logger.h"
#include "../../include/mongodb.h"
// Third-party headers
#include <mongocxx/client.hpp>
#include <nlohmann/json.hpp>
Security
Validate input; use prepared statements; rate limit APIs; sanitize URLs; validate email/mobile formats.
Performance
Connection pooling (MongoDB); Redis caching; minimize DB round trips; indexes on hot fields.
Memory and Threads
Smart pointers; RAII; mutexes for shared state; lock_guard; minimize lock scope.
Testing
- MongoDB:
docker exec mongodb_test mongosh --username admin --password password123 --eval "db.adminCommand('ping')" - API:
curl --location 'http://localhost:3000/api/endpoint' --header 'Content-Type: application/json' --data-raw '{ ... }' - Verify data:
docker exec mongodb_test mongosh --username admin --password password123 --eval "use('search-engine'); db.collection.find().pretty()" - Logs:
docker logs core --tail 50,docker logs mongodb_test
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.
- 2d ago First seen · 52 lines · 352 tokens per session scan A 02bdf7e25c50
search-engine-core code-style.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 352 tokens to every session, about $0.0018 per session on Opus 5. A static security scan graded it A with 2 findings (sends data to an external url, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other instructions, from other repositories
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).
electron CLAUDE.md
Instructions for electron/electron, covering electron development guide, running nodemodules binaries, project overview, directory structure and build tools setup.
electron copilot-instructions.md
Instructions for electron/electron, covering copilot instructions for electron, build system, linting, running a single test and example: npm run test -- -g "ipc".
compiler-explorer AGENTS.md
Instructions for compiler-explorer/compiler-explorer, covering agents.md, build & test commands, important workflow requirements, style guidelines and architecture guidelines.
weaviate CLAUDE.md
Instructions for weaviate/weaviate, covering claude.md, no bug is ever out of scope, build & run, build the binary (cgoenabled=0, static linking) and build debug binary (with delve support).
compiler-explorer copilot-instructions.md
Instructions for compiler-explorer/compiler-explorer: For each answer to the user, evaluate your level of confidence in the correctness of the answer on a scale from 1 to 10, where 1 is very uncertain and 10 is absolutely certain. If your confidence level is below 8, state so and suggest ways to verify the answer.