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.
git clone --depth 1 https://github.com/hatefsystems/search-engine-coreWrote 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.
[](https://agentmods.dev/rules/hatefsystems/search-engine-core/build-deployment)<a href="https://agentmods.dev/rules/hatefsystems/search-engine-core/build-deployment"><img src="https://agentmods.dev/badge/rules/hatefsystems/search-engine-core/build-deployment/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.
<a href="https://agentmods.dev/rules/hatefsystems/search-engine-core/build-deployment"><img src="https://agentmods.dev/badge/rules/hatefsystems/search-engine-core/build-deployment.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.1 | $0.00008 | $0.00184 |
| Opus 5.5 | $0.00003 | $0.00074 |
| Sonnet 5.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 1mo 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.
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.
- 1mo ago 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 today), licensed Apache-2.0. It adds 8 tokens to every session and 184 once invoked, about $0.0000 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.
Other cursor rules, from other repositories
kubernetes
Kubernetes and OpenShift workload generation rules — security defaults, resource limits, probes.
kubernetes
This guide defines definitive best practices for writing, organizing, and securing Kubernetes manifests and Operators, ensuring maintainable, performant, and reliable cloud-native deployments.
aws-ecs
Definitive guidelines for building, deploying, and operating applications on AWS ECS, emphasizing immutable containers, secure secrets management, and robust operational patterns.
kubernetes-helm
Kubernetes and Helm best practices including resource management, security, chart organization, and deployment patterns.
deployment
Rails Deployment with Kamal.
docker-deployment
Complete Docker containerization, production deployment, and monitoring patterns for POS System.