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/hamzaamjad/cursor-rulesWrote 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/hamzaamjad/cursor-rules/000-core-rulesync)<a href="https://agentmods.dev/rules/hamzaamjad/cursor-rules/000-core-rulesync"><img src="https://agentmods.dev/badge/rules/hamzaamjad/cursor-rules/000-core-rulesync/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/hamzaamjad/cursor-rules/000-core-rulesync"><img src="https://agentmods.dev/badge/rules/hamzaamjad/cursor-rules/000-core-rulesync.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.00769 | $0.00769 |
| Opus 5.5 | $0.00308 | $0.00308 |
| Sonnet 5.5 | $0.00154 | $0.00154 |
| Haiku 4.5 | $0.00077 | $0.00077 |
Grade B, and why
000-core-rulesync scanned grade B 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
- May run bash/python snippets directly (no sudo without explicit permission) How it starts
The opening of the file, as written. The whole thing — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AI Assistant Rules for The Mirror Project
Core Philosophy
You are assisting with The Mirror Project - a local-first, privacy-respecting AI workspace that unifies LLMs, personal health & context streams, and autonomous agents. Always prioritize:
- Information density and engineering precision
- Privacy and local-first architecture
- Practical, working solutions over theoretical discussions
Communication Style
- Be information-dense and engineering-precise; avoid fluff
- Default to "you can do this" coaching tone
- Ask clarifying questions ONLY when ambiguity blocks action
- Prefer primary sources and official documentation; always cite links
Code Standards
- Language: Python 3.11+ with type hints
- Framework: FastAPI with Pydantic v2 for APIs
- Style: Well-commented, runnable code with minimal external dependencies
- Testing: Maintain 80%+ coverage with descriptive test names
- Security: Never commit secrets, validate all inputs, use secure defaults
Output Formats
- Code: Properly formatted with comments, ready to run
- Tasks: Numbered checklists or YAML/JSON specs ready for agents
- Documentation: Markdown with clear heading hierarchy and links
- Diagrams: Mermaid for architecture, tables for comparisons
Technology Stack
Core
- Python 3.11, FastAPI, Pydantic v2, Poetry/venv
- PostgreSQL + TimescaleDB, Redis, Docker
- GitHub Actions for CI/CD
ML/LLM
- HuggingFace (transformers, accelerate)
- Diffusion-based LLaDA-8B
- Vector stores (Chroma), RAG implementations
Infrastructure
- Kubernetes-lite (k3d), Prometheus + Grafana
- Pulumi (TypeScript) for IaC
- Git-secrets pre-commit hooks
Project-Specific Context
- Building local-first health data integration (WHOOP, Oura, Tomorrow.io)
- Implementing FastAPI/OpenAI-style endpoints
- Creating Grafana dashboards for visualization
- Ensuring GitHub Actions CI/CD with act-local parity
Development Workflow
- Rapid prototyping with edge-case thinking
- Test coverage for all new features
- Clear documentation in README/AGENTS.md
- Containerized, production-ready deployments
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 · 89 lines · 769 tokens per session scan B ea41b08ed75f
000-core-rulesync is a cursor rule published in the GitHub repository hamzaamjad/cursor-rules (2 stars, last pushed 1y ago), licensed MIT. It adds 769 tokens to every session, about $0.0031 per session on Opus 5.5. A static security scan graded it B with 1 finding (asks for root). 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-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.
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).