Borrowing it
Nothing to install: this file belongs to oleksiitrembach/gigaspec. 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/oleksiitrembach/gigaspec/main/.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/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/oleksiitrembach/gigaspec/cursorrules"><img src="https://agentmods.dev/badge/rules/oleksiitrembach/gigaspec/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.00088 | $0.00088 |
| Opus 5.5 | $0.00035 | $0.00035 |
| Sonnet 5.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 2mo 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.
- 2mo 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 8mo ago), licensed Apache-2.0. It adds 88 tokens to every session, about $0.0004 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-31.
Other cursor rules, from other repositories
swamr-orchestrator
Swamr Orchestrator — autonomous agent swarm that builds entire projects. Invoke with @swamr-orchestrator followed by what you want built. Decomposes into tasks, selects specialist agents, runs dev↔QA loops, and delivers production-ready code.
swamr-planner
Swamr Planner — generates detailed project plans with task decomposition, dependency graphs, and agent assignments. Use @swamr-planner to plan before building, or let the orchestrator invoke it automatically.
swamr-skill-selector
Swamr Skill Selector — automatically picks the right specialist agent for any task based on the task description, tech stack, and project context. Used internally by the orchestrator.
swamr-obsidian-brain
Swamr Obsidian Brain — persistent knowledge base that agents read from and write to across phases. Prevents context loss by maintaining architecture decisions, task outputs, learned patterns, and project knowledge in an Obsidian vault. Every agent MUST read relevant notes before starting and write a summary note when…
swamr-browser-agent
Swamr Browser Agent — handles tasks that require browser automation via Playwright. Sets up Supabase projects, configures OAuth providers, runs visual tests, and interacts with web UIs that don't have CLI/API alternatives.
swamr-qa-loop
Swamr QA Loop — validates every task output through automated and manual checks. Invoked automatically by the orchestrator after each task completion. Enforces quality gates with evidence-based pass/fail decisions.