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/IgorKrupenja/buerokratt-mcpWrote 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/igorkrupenja/buerokratt-mcp/cursorrules)<a href="https://agentmods.dev/rules/igorkrupenja/buerokratt-mcp/cursorrules"><img src="https://agentmods.dev/badge/rules/igorkrupenja/buerokratt-mcp/cursorrules/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/igorkrupenja/buerokratt-mcp/cursorrules"><img src="https://agentmods.dev/badge/rules/igorkrupenja/buerokratt-mcp/cursorrules.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.04062 | $0.04062 |
| Opus 5.5 | $0.01625 | $0.01625 |
| Sonnet 5.5 | $0.00812 | $0.00812 |
| Haiku 4.5 | $0.00406 | $0.00406 |
Grade A, and why
cursorrules 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 2mo 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 — 321 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cursor Rules for Service-Module Repository
⚠️ WARNING: THIS FILE IS NOT USED BY MCP SERVER ⚠️
This is an example/reference file showing the original .cursorrules format from Service-Module.
The MCP server uses the modular rules structure in the rules/ directory instead.
This file is kept here for reference only and should not be used normally.
It is not guaranteed to be up to date with the MCP server rules in the rules/ directory.
Project Overview
This repository contains a Service Module with two main parts:
- GUI folder: React-based front-end application (contains all frontend code and tests)
- DSL folder: Back-end using a custom stack (configuration-based, no unit tests)
Back-End
Database Migrations
- Migration Location: SQL migrations are in
DSL/Liquibase/changelog/folder - Migration Format: Check latest files in
Liquibase/changelogfolder for current format - Three Files Required: When creating migrations, ALWAYS create three files:
- XML file:
YYYYMMDDHHMMSS_description.xmlinchangelog/folder - SQL file:
YYYYMMDDHHMMSS_description.sqlinchangelog/migrations/folder - Rollback file:
YYYYMMDDHHMMSS_rollback.sqlinchangelog/migrations/rollback/folder
- XML file:
- File Naming: Use timestamp format
YYYYMMDDHHMMSSfollowed by descriptive name - XML Structure: Include proper XML headers and changeSet with sqlFile and rollback sections
- Legacy Migrations: Do NOT modify old migrations in legacy format (direct .sql files)
- Local Execution: Run migrations locally with
migrate.shin repo root - Author Format: Use GitHub username in changeSet. Get username with
git remote get-url origin | sed 's/.*github.com[:/]\([^/]*\)\/.*/\1/'
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.
- 2mo ago First seen · 321 lines · 4,062 tokens per session scan A 75b3815ab818
cursorrules is a cursor rule published in the GitHub repository IgorKrupenja/buerokratt-mcp (1 stars, last pushed 6mo ago), licensed MIT. It adds 4,062 tokens to every session, about $0.0162 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
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
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.
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.
config-validation-and-normalization
Config validation and normalization responsibilities (defineConfig normalizes, the orm section schema validates and resolves paths, the loader reports per-section diagnostics).
control-plane-descriptors
Control plane descriptor and instance implementation patterns.