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/e-gov/cursor-prompts/component-technical-standardsgit clone --depth 1 https://github.com/e-gov/cursor-promptsWhat 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.01253 | $0.01253 |
| Opus 5 | $0.00626 | $0.00626 |
| Sonnet 5 | $0.00251 | $0.00251 |
| Haiku 4.5 | $0.00125 | $0.00125 |
Grade A, and why
component-technical-standards 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 2d 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 — 131 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Component Technical Standards
Context and Purpose
Target Audience: Software developers, AI coding assistants, automated code review tools Scope: Enterprise software component development for SMIT platform Purpose: Automatically enforceable technical standards and implementation patterns
These standards are designed to be validated automatically during development by AI assistants and code analysis tools. They focus on component architecture patterns, integration approaches, technical implementation details, and best practices that can be mechanically verified.
Complementary Documents: See rules/common/security.mdc and rules/common/integration-standards.mdc.
Requirements
Component Architecture
Code Quality & Standards
- Source code must be UTF-8 formatted
- Move textual values to translation files (i18n)
- NEVER use deprecated methods
- Code and comments must be in English; business variables in Estonian if no logical equivalent exists
- Build artifacts must be deployable to different environments without rebuilding
- Logic components should follow a layered architecture (e.g., MVC or hexagonal) with clear separation of concerns
- Mark audit log entries clearly to distinguish them in log searches
- Remove unused/dead code and commented-out blocks; rely on version control history instead of commented code
- Declare all dependencies via manifest files and lock versions for reproducible builds
Database & Data Management
- Create migration scripts for data object changes - run during deployment, not on every restart
- NEVER write business logic in database (procedures, triggers) without explicit justification in architecture documentation
- Use full-text indexes (Lucene or database internal) for text searches only
- Access databases only through application-specific system users, NEVER through superuser accounts (SYS, POSTGRES)
- Use registry codes with country prefix (ISO 3166-1 Alpha-2, uppercase) for object identification
- Each component must own its database; different components MUST NOT share the same database
- Databases MUST NOT be used as an integration mechanism between components
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.
- 2d ago First seen · 131 lines · 1,253 tokens per session scan A 0573d4d2d704
component-technical-standards is a cursor rule published in the GitHub repository e-gov/cursor-prompts (34 stars, last pushed 4mo ago), licensed MIT. It adds 1,253 tokens to every session, about $0.0063 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-30.
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.
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.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.
family-instance-domain-actions
Family instance domain action implementation patterns.