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/oleksiitrembach/gigaspec/cursorrulesgit clone --depth 1 https://github.com/oleksiitrembach/gigaspecWrote 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/oleksiitrembach/gigaspec/cursorrules)<a href="https://agentmods.dev/rules/oleksiitrembach/gigaspec/cursorrules"><img src="https://agentmods.dev/badge/rules/oleksiitrembach/gigaspec/cursorrules.svg" alt="Measured on agentmods" 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 | $0.00088 | $0.00088 |
| Opus 5 | $0.00044 | $0.00044 |
| Sonnet 5 | $0.00018 | $0.00018 |
| Haiku 4.5 | $0.00009 | $0.00009 |
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 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.
What it actually says
MyProject - Cursor Rules
ALWAYS
- Read STATE.md first
- Check AGENT.md constraints
- Max 10 lines per function
NEVER
- Skip verification
- Update STATE.md without CONFIRMED
COMMANDS
- "Familiarize yourself" - Read all docs
- "CONTINUE" - Next task from STATE.md
- "STATUS" - Current state
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 · 13 lines · 88 tokens per session scan A 02b8722a80f2
cursorrules is a cursor rule published in the GitHub repository oleksiitrembach/gigaspec (0 stars, last pushed 6mo ago), licensed Apache-2.0. It adds 88 tokens to every session, about $0.0004 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
edt-form-xml-requirements
Требования EDT к XML-формам (Form.form): extInfo, дефолты полей.
async-methods-1c
Асинхронные методы 1С: Асинх/Ждать/Обещание (8.3.18+).
1c-form-reserved-names
Зарезервированные имена свойств в модулях форм 1С.
routine_assignment_ext_processor
Фоновые задания из внешней обработки через БСП.
edt-bsl-write-safety
Безопасная запись BSL-модулей через EDT MCP (режимы writemodulesource).
cursorrules
Root AI front door (this file). Depth: docs/AGENTS.md · Claude: docs/CLAUDE.md · Antigravity: docs/GEMINI.md · map: llms.txt Read first: docs/ai/INDEX.md → docs/ai/CANONICAL.md → docs/ai/COREREFERENCE.md Packages: docs/guides/ecosystem.md — GEMVC is a multi-package ecosystem (vendor/gemvc/). Core: gemvc/helper…