Borrowing it
Nothing to install: this file belongs to mikiships/agentmd. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/mikiships/agentmd/main/.cursorrulesgit clone --depth 1 https://github.com/mikiships/agentmdWrote 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/mikiships/agentmd/cursorrules)<a href="https://agentmods.dev/rules/mikiships/agentmd/cursorrules"><img src="https://agentmods.dev/badge/rules/mikiships/agentmd/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/mikiships/agentmd/cursorrules"><img src="https://agentmods.dev/badge/rules/mikiships/agentmd/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.00552 | $0.00552 |
| Opus 5.5 | $0.00221 | $0.00221 |
| Sonnet 5.5 | $0.00110 | $0.00110 |
| Haiku 4.5 | $0.00055 | $0.00055 |
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 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 — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
.cursorrules
Cursor IDE rules. These rules are applied to every AI interaction in this project.
Always
- Read the relevant source files before making changes.
- Make minimal, targeted edits — avoid reformatting unrelated code.
- Respect the existing code style (indentation, naming, import order).
- Run
python3 -m pytest tests/ -xafter every non-trivial change. - Run
ruff check . && ruff format --check .before finalizing changes. - Add type annotations to all new public functions.
- Use
pathlib.Pathinstead ofos.pathfor file operations.
Never
- Never commit API keys, tokens, or credentials.
- Never delete tests to make the suite pass.
- Never use
TODOcomments without a linked issue or explanation. - Never make changes outside the scope of the current task without flagging them.
- Never use
except:without specifying the exception type. - Never use
eval()orexec()on untrusted input.
Project Overview
Primary languages: Python Package managers: pip CI: GitHub Actions
Build, Test, and Lint Commands
Install dependencies:
pip install -e '.[dev]'
Run tests:
python3 -m pytest tests/ -x
Lint / format:
ruff check . && ruff format --check .
Directory Structure
Top-level directories: .github, agentmd, tests
Test roots: tests
Most-changed directories: agentmd, tests, README.md, pyproject.toml, progress-log.md
File Patterns
Test files: tests/**
Python source: **/*.py
Python tests: **/test_*.py, **/*_test.py
Conventions Inferred from Codebase
Commit prefix style: feat, fix, chore, docs, feat(d3) (follow this pattern)
Common file extensions: .pyc, .py, .md, .toml, .yml
- Python: use type hints on all public functions
- Python: snake_case for functions/variables, PascalCase for classes
- Tests: files named
test_*.py, functions namedtest_*
Context Preferences
When writing or reviewing code, prefer to include in context:
tests/(primary code locations)- The file being edited and its direct imports.
- Relevant test files alongside source files.
- Configuration files when modifying build or tooling behavior.
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 · 64 lines · 552 tokens per session scan A d6dd9c33ccc0
cursorrules is a cursor rule published in the GitHub repository mikiships/agentmd (12 stars, last pushed 7mo ago), licensed MIT. It adds 552 tokens to every session, about $0.0022 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
hatch3r-dynamic-stack-verification
Runtime-evidence gates for stacks with no static type layer (plain-JS Vue, dynamic persistence) — smoke-mount changed components, dormant-collection-read ratchet, runtime smoke evidence on module-boundary changes; a green lint+build+mock-suite proves a layer, not the system.
hatch3r-migrations
Database migration and schema change patterns — expand-contract, online DDL, backfills, compatibility windows, reversibility, multi-region, tooling.
hatch3r-scalability
CQ6 Scalability Quality measurement rule — stateless-handler ratio, back-pressure pattern adoption, idempotency-key adoption on POST/PUT/PATCH, queue offloading for >1s ops, pool sizing per concurrency profile.
hatch3r-data-classification
Data classification standards covering PII handling, encryption, retention policies, and regulatory compliance.
hatch3r-observability-logging
Structured logging and error reporting conventions for the project.
tools
(none|read|write|network|exec) and risk (low|medium|high|critical). These drive the permission classifier — be honest.