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/glideapps/mcp/glideos-developmentgit clone --depth 1 https://github.com/glideapps/mcpWhat 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.00020 | $0.00226 |
| Opus 5 | $0.00010 | $0.00113 |
| Sonnet 5 | $0.00004 | $0.00045 |
| Haiku 4.5 | $0.00002 | $0.00023 |
Grade A, and why
glideos-development 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 yesterday.
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.
What it actually says
Working with Glide
These conventions apply when using the glide MCP server tools.
Before writing app code
Read the app-building contract resource at glideos://guidance/app-building-contract before writing or modifying GlideOS application code. It is the canonical contract for how GlideOS apps are structured and must be followed.
Additional in-depth GlideOS skills and capability guidance are available as MCP resources on this server. Read the relevant resources before doing work they govern.
Projects
Most tools operate on a project. If the user has not identified a project, list their projects first and confirm which one to work in before making changes.
Authentication
Signing in happens through Glide's OAuth flow the first time a tool is used. The connected user's organization determines which projects and data are accessible.
Destructive operations
Deleting apps, dropping tables, restoring backups, and rolling back releases affect live user data. Confirm the target and the intent with the user before running them.
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.
- yesterday First seen · 27 lines · 20 tokens per session scan A 847fd98ccdac
glideos-development is a cursor rule published in the GitHub repository glideapps/mcp (0 stars, last pushed 3d ago), licensed MIT. It adds 20 tokens to every session and 226 once invoked, about $0.0001 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.
typescript
Changes to these high-fan-out internals can affect every message, delta, element, or rerun. Keep work in them minimal, and benchmark changes with representative stress-test apps.
coolify-ai-docs
Master reference to all Coolify AI documentation in .ai/ directory.
python_lib
Tips and guidelines specific to the development of the Streamlit Python library, not applicable to scripts and e2e tests.
specs
This directory contains product and tech specs for Streamlit features.