llms.txtA
llms.txt from phaedra-solutions/cursor-rules is an llms.txt file: plain text a project publishes for AI models to read.
mdr add phaedra-solutions/cursor-rules/llms.txt@git:20261102.23e540dPins git:20261102.23e540d in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 14 of 14 checks passed
- Kind
- llms.txt file
- Repository
- phaedra-solutions/cursor-rules
- Path
llms.txt- Versions recorded
- 1
- Latest version
- git:20261102.23e540d, committed Nov 2, 2026
- Size
- 5,162 bytes
- Repository stars
- 4
- License
- MIT
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# cursor-rules > Version-aware, security-first coding rules and Agent Skills for AI coding agents, maintained by Phaedra Solutions under the MIT license. One Markdown source builds Cursor project rules (`.cursor/rules/*.mdc`), `AGENTS.md`, `CLAUDE.md` and Agent Skills (`SKILL.md`) for Cursor, Claude Code, OpenAI Codex, GitHub Copilot and Gemini CLI. Each stack rule first reads the installed framework version from the lockfile, then applies current conventions, security controls mapped to OWASP Top 10:2025 and the CWE Top 25, a dated known-vulnerabilities table with minimum safe versions, and the exact lint, typecheck, test and audit commands to run. Below a rule's supported range, the agent follows a `legacy/` rule and `core/legacy-mode`: minimal changes, end-of-life status, compensating controls and a migration skill. Install from a clone with Node.js 22+ and no dependencies: `node scripts/install.mjs --preset <name> --tool cursor,agents,claude --dest <project> --dry-run`, then run it again without `--dry-run`. Archives for each tool, with `SHA256SUMS`, are attached to every GitHub Release. ## Docs …
Read the whole file at its exact version.
How to install
mdr add phaedra-solutions/cursor-rules/llms.txt@sha256:271b97c8056c62f2The line at the top of this page pins the label git:20261102.23e540d, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_yutj5vi7qyomd7pv)
2 badge image fetches in 30 days. What the badge shows.
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it: what changed in phaedra-solutions/cursor-rules/llms.txt since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.
Got a copy of llms.txt from somewhere else? Ask it: where did my llms.txt come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.
Versions
The registry has recorded 1 version of this file, committed on Nov 2, 2026.
Watch this file (sign in, one email per new version)
Installed this file, say at llms.txt? Drop it here to learn which saved version you have and what changed since. Your browser works out its SHA-256 fingerprint and sends only that; the file itself never leaves your computer.
Or paste its contents
Your agent can run this same check on the agent markdown files you have installed, up to 50 in one ask. Add the registry once:
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it to check the files you have installed. No key and no account.
From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies
In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies
No sha256sum on your machine? shasum -a 256 prints the same lines.
Audit of the latest version
- pass: Size between 200 bytes and 200 KB (5162 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
phaedra-solutions/cursor-rules · 4 stars · license MIT · pushed 2026-11-02 · branch master
API
GET https://markdownregistry.com/api/v1/artifacts/art_yutj5vi7qyomd7pv GET https://markdownregistry.com/api/v1/resolve?ref=phaedra-solutions/cursor-rules/llms.txt GET https://markdownregistry.com/api/v1/blob/271b97c8056c62f24351beaeab92bd17bdc6cc54b0dc8130146df0d7cefc5fbb
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: how to add an llms.txt file to a website · which agent file does what.
More from phaedra-solutions/cursor-rules
Every file in phaedra-solutions/cursor-rules