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/KhaledSaeed18/node-express-boilerplateWrote 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/khaledsaeed18/node-express-boilerplate/conventions)<a href="https://agentmods.dev/rules/khaledsaeed18/node-express-boilerplate/conventions"><img src="https://agentmods.dev/badge/rules/khaledsaeed18/node-express-boilerplate/conventions/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/khaledsaeed18/node-express-boilerplate/conventions"><img src="https://agentmods.dev/badge/rules/khaledsaeed18/node-express-boilerplate/conventions.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.00664 | $0.00664 |
| Opus 5.5 | $0.00266 | $0.00266 |
| Sonnet 5.5 | $0.00133 | $0.00133 |
| Haiku 4.5 | $0.00066 | $0.00066 |
Grade A, and why
conventions 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.
How it starts
The opening of the file, as written. The whole thing — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Hard Rules
Environment variables: Never use process.env directly anywhere. Import the typed config object from src/config/env.ts.
Error handling: Throw from src/errors/index.ts. In controllers, always catch and call this.handleError(error, next) — never res.status().json() on error paths. Available classes: AppError, ValidationError, AuthenticationError, AuthorizationError, NotFoundError, ConflictError, InternalServerError.
Logging: Use the Pino logger from src/config/logger.ts. Never use console.log/warn/error.
Validation: Zod v4 schemas in src/validations/. Use validateBody(schema) from src/lib/validate.ts to produce middleware. Export both the schema type and the RequestHandler from the validation file.
Package manager: pnpm only. Never generate package-lock.json or yarn.lock.
TypeScript
- Strict mode — no
any, no@ts-ignore - All type-only imports must use
import type - Explicit return types on all public methods and class properties
- No floating promises — always
awaitor.catch() - Prefer
??over||for nullish checks
Formatting (Prettier)
4-space indent · single quotes · semicolons · trailing commas · 100-char line limit
Controller Pattern
Controller methods are arrow function properties (not regular methods) so this is bound correctly when passed as route handlers:
public createFoo = async (req: Request, res: Response, next: NextFunction): Promise<void> => {
try {
// ...
this.sendResponse(res, 201, 'Foo created', data);
} catch (error) {
this.handleError(error, next);
}
};
Repository Pattern
- Extend
BaseRepository - Use
this.prisma.<model>for all queries - In
update/delete, wrap Prisma calls in try/catch and callthis.handlePrismaError(error) - Use
this.findManyWithPagination()andthis.count()from the base class for list/count operations
Route Pattern
export class FooRoute extends BaseRoute {
private fooController!: IFooController;
protected initializeRoutes(): void {
this.fooController = this.container.getFooController();
this.router.post('/', fooLimiter, protect, createFooValidation, this.fooController.createFoo);
// ...
}
}
const fooRoute = new FooRoute();
const fooRoutes = fooRoute.getRouter();
export default fooRoutes;
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 · 77 lines · 664 tokens per session scan A 849c9b159b84
conventions is a cursor rule published in the GitHub repository KhaledSaeed18/node-express-boilerplate (36 stars, last pushed 5d ago), licensed MIT. It adds 664 tokens to every session, about $0.0027 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-30.
Other cursor rules, from other repositories
shared-plane-packages
Pattern for creating shared plane packages that serve both migration and runtime planes.
sql-queries-not-asts
Name built-and-lowered SQL units "queries", not "asts".
query-patterns
Standard patterns for working with Prisma 8 queries.
architecture
Architecture of openapi-to-cli (ocli).
grab
Version: v2.0.0 Last Updated: 2025-12-10 Purpose: Developer guidelines for building APIs with GRAB (Go REST API Boilerplate).
server-patterns
Rules for server-side Express code.