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/secondlifes/delphi-expert/horse-patternsgit clone --depth 1 https://github.com/SecondLifes/delphi-expertWrote 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/secondlifes/delphi-expert/horse-patterns)<a href="https://agentmods.dev/rules/secondlifes/delphi-expert/horse-patterns"><img src="https://agentmods.dev/badge/rules/secondlifes/delphi-expert/horse-patterns.svg" alt="Measured on agentmods" 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 | $0.00000 | $0.00401 |
| Opus 5 | $0.00000 | $0.00200 |
| Sonnet 5 | $0.00000 | $0.00080 |
| Haiku 4.5 | $0.00000 | $0.00040 |
Grade A, and why
horse-patterns 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
Horse Framework — Rules
Use these rules when developing REST APIs with the Horse framework.
Controller Structure
- Controller is a class with
class procedure RegisterRoutes - Cada handler:
class procedure Nome(AReq: THorseRequest; ARes: THorseResponse; ANext: TProc) - Controllers DO NOT access the database directly — they delegate it to Services
Route Conventions
| verb | Route | handlers | Status |
|---|---|---|---|
| GET | /api/customers |
GetAll |
200 |
| GET | /api/customers/:id |
GetById |
200 / 404 |
| POST | /api/customers |
Create |
201 |
| PUT | /api/customers/:id |
Update |
200 |
| DELETE | /api/customers/:id |
Delete |
204 |
Mandatory Middleware
THorse.Use(Jhonson); //Automatic JSON
THorse.Use(CORS); //Cross-Origin
THorse.Use(HandleException); // Error handler global
Response Patterns
//Success with JSON
ARes.Send<TJSONObject>(LResult).Status(THTTPStatus.OK);
//Creation
ARes.Send('Created').Status(THTTPStatus.Created);
//Not found
ARes.Send('Not found').Status(THTTPStatus.NotFound);
//Validation error
ARes.Send(E.Message).Status(THTTPStatus.BadRequest);
Bans on Horse
- ❌ Access
TFDConnectiondirectly from the controller - ❌ Business logic in the handler
- ❌ Routes without error handling
- ❌ Concatenate SQL in the controller
- ❌ Ignore HTTP status
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 · 58 lines · 0 tokens per session scan A cc7cf16a7a55
horse-patterns is a cursor rule published in the GitHub repository SecondLifes/delphi-expert (3 stars, last pushed 3d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 401 tokens. 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-09-03.
Other cursor rules, from other repositories
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
family-instance-domain-actions
Family instance domain action implementation patterns.
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.