Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/hatefsystems/search-engine-corenpx agentmods add rules/hatefsystems/search-engine-core/testingWrote 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/testing)<a href="https://agentmods.dev/rules/hatefsystems/search-engine-core/testing"><img src="https://agentmods.dev/badge/rules/hatefsystems/search-engine-core/testing/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/testing"><img src="https://agentmods.dev/badge/rules/hatefsystems/search-engine-core/testing.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.02248 | $0.02248 |
| Opus 5.5 | $0.00899 | $0.00899 |
| Sonnet 5.5 | $0.00450 | $0.00450 |
| Haiku 4.5 | $0.00225 | $0.00225 |
Grade A, and why
testing scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
response=$(curl -s -X POST "$API_URL/api/endpoint" \ How it starts
The opening of the file, as written. The whole thing — 389 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Testing Standards and Organization
Test Directory Structure
tests/
├── integration/ # Integration tests (API, end-to-end)
│ ├── README.md
│ ├── test_profile_api.sh
│ ├── test_link_blocks.sh
│ ├── test_website_profile_api.sh
│ └── test_10_concurrent.sh
├── common/ # C++ unit tests for common utilities
├── crawler/ # C++ unit tests for crawler
├── models/ # C++ unit tests for models
├── privacy/ # C++ unit tests for privacy/encryption
├── scoring/ # C++ unit tests for scoring
├── search_core/ # C++ unit tests for search engine core
├── storage/ # C++ unit tests for storage layer
├── text_processing/ # C++ unit tests for text processing
└── webserver/ # C++ unit tests for webserver
scripts/ # Utility scripts (not tests)
Test File Naming
Shell Integration Tests
- Format:
test_<feature_name>.sh - Location:
tests/integration/ - Examples:
test_profile_api.sh- Profile CRUD operationstest_link_blocks.sh- Link blocks and analyticstest_10_concurrent.sh- Concurrent request handling
C++ Unit Tests
- Format:
test_<component>.cpp - Location:
tests/<component>/ - Examples:
tests/storage/test_profile_storage.cpptests/crawler/test_url_parser.cpp
Shell Test Script Standards
Required Structure
#!/bin/bash
set -e # Exit on error
# Color codes for output
RED='\033[0;31m'
GREEN='\033[0;32m'
YELLOW='\033[1;33m'
NC='\033[0m'
# Configuration
API_URL="${API_BASE_URL:-http://localhost:3000}"
echo "Testing Feature Name..."
# Test functions
test_feature_creation() {
echo "Test: Create feature..."
# ... test implementation
echo -e "${GREEN}✅ Feature creation successful${NC}"
}
# Run tests
test_feature_creation
# ... more tests
# Cleanup
cleanup() {
echo "Cleaning up test data..."
# ... cleanup implementation
}
trap cleanup EXIT
echo "All tests passed!"
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 · 389 lines · 2,248 tokens per session scan A 19c4f30f1188
testing is a cursor rule published in the GitHub repository hatefsystems/search-engine-core (5 stars, last pushed today), licensed Apache-2.0. It adds 2,248 tokens to every session, about $0.0090 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). 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
300-testing
Comprehensive testing guide covering unit, integration, E2E, test frameworks, patterns, and CI/CD integration.
hatch3r-testing
Coverage thresholds, mocking strategy, property-based testing, mutation-score targets, flaky test quarantine, and snapshot test discipline.
testing
Cursor rule "testing" from andersonlemesc/Oryntra, covering testes oryntra, laravel (pest), python (pytest), contract tests (laravel ↔ python) and browser/e2e.
30-testing
Convenciones de testing, cobertura mínima, tipos de tests, mocks.
tester
Tester role - Unit, E2E, and visual regression testing.
go-test
Rules for writing and modifying test files (test.go) in go-crypto-wallet.