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/build-deploymentgit 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.00008 | $0.00184 |
| Opus 5 | $0.00004 | $0.00092 |
| Sonnet 5 | $0.00002 | $0.00037 |
| Haiku 4.5 | $0.00001 | $0.00018 |
Grade A, and why
build-deployment 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
Build and Deployment
Local build
cd /root/search-engine-core && mkdir -p build && cd build
cmake .. && make -j4
Docker
docker cp /root/search-engine-core/build/server core:/app/server
docker restart core
# or: docker compose up --build
CMake
When adding new storage classes:
- Add to
src/storage/CMakeLists.txt - Create static library target
- Link to main server executable
- Include in install targets
Production Deployment
- Set appropriate environment variables
- Enable HTTPS
- Configure proper MongoDB authentication
- Set up monitoring and alerting
- Implement backup strategies
- Use production Docker images from GHCR
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 · 39 lines · 8 tokens per session scan A 1b0fbd2f037a
build-deployment 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 8 tokens to every session and 184 once invoked, about $0.0000 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.