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/francescogabrieli/glyph/projectgit clone --depth 1 https://github.com/francescogabrieli/glyphWhat 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.00740 | $0.00740 |
| Opus 5 | $0.00370 | $0.00370 |
| Sonnet 5 | $0.00148 | $0.00148 |
| Haiku 4.5 | $0.00074 | $0.00074 |
Grade A, and why
project 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 — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cursor Project Rules
Read relevant files before editing. Create a short plan before changing database schema, authentication, or shared components. Keep changes small and reviewable. Prefer simple explicit code. Follow existing repository conventions.
- Before marking work done, run the relevant tests.
- Run lint before done.
- Run type checks before done.
- Do not add unrequested features.
- Avoid large refactors and broad rewrites.
- Report what changed and report what was verified.
- If verification was skipped, explain unrun tests.
Commands:
pnpm install
pnpm dev
pnpm test
pnpm lint
pnpm build
Security:
Never commit secrets, credentials, API keys, tokens, or private keys. Ask for confirmation before destructive operations, schema changes, unsafe migrations, and security-sensitive changes. Do not deploy without approval.
Do not edit generated files manually. Use shared database helpers rather than raw connections.
Repository notes
Cursor rules often mix direct behavioral instructions with notes about editor behavior, generated files, and project conventions. This project keeps reusable data access helpers in a shared package so services do not open ad hoc database connections. That guidance is repository-specific and useful, but it is not a universal Glyph semantic unit unless a custom rule is supplied.
The benchmark keeps frontmatter, checklist-like rules, command blocks, safety notes, and prose in one file because real .mdc files commonly combine those forms. The structural parser should keep line numbers and section context so inspect output is actionable.
Cursor workflow
Always read relevant files before editing. Create a short plan before non-trivial edits. Make the smallest safe change. Follow existing style, prefer existing patterns, and keep changes small and reviewable.
Use shared database helpers rather than raw connections. Use existing shared helpers before introducing new abstractions. Avoid unrelated packages. Respect package boundaries and ask before touching another workspace.
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 · 73 lines · 740 tokens per session scan A def5b0252c8e
project is a cursor rule published in the GitHub repository francescogabrieli/glyph (7 stars, last pushed 1mo ago), licensed MIT. It adds 740 tokens to every session, about $0.0037 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-31.
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.