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.
git clone --depth 1 https://github.com/Elumenotion/GuideAntsWrote 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/elumenotion/guideants/project-rules)<a href="https://agentmods.dev/rules/elumenotion/guideants/project-rules"><img src="https://agentmods.dev/badge/rules/elumenotion/guideants/project-rules/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/elumenotion/guideants/project-rules"><img src="https://agentmods.dev/badge/rules/elumenotion/guideants/project-rules.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.01168 | $0.01168 |
| Opus 5.5 | $0.00467 | $0.00467 |
| Sonnet 5.5 | $0.00234 | $0.00234 |
| Haiku 4.5 | $0.00117 | $0.00117 |
Grade A, and why
project-rules 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 1mo 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 — 213 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GuideAnts Project Rules
Project Structure
root/
├── client/ # Frontend Electron application
│ ├── src/ # Source code for React application
│ ├── electron/ # Electron-specific code
│ ├── public/ # Static assets
│ ├── dist/ # Build output
│ └── resources/ # Application resources
└── server/ # Backend .NET application
├── GuideAntsApi/ # Main API project
├── GuideAntsApi.DataModel/ # Data models and EF Core
└── code-interpreter/ # Code interpretation services
Technology Stack Requirements
Frontend
- Electron: ^36.3.1
- Vite: ^6.3.5
- React: ^19.1.0
- TypeScript: ^5.8.3
- TailwindCSS: ^3.4.1
Backend
- ASP.NET Core: ^8.0
- Entity Framework Core: ^8.0
- SQL Server Database
- Azure AD Authentication
Development Standards
General
- All new code must be written in TypeScript (frontend) or C# (backend)
- Use UTF-8 encoding for all text files
- Use LF (\n) for line endings
- Maximum line length: 120 characters
- Follow semantic versioning (MAJOR.MINOR.PATCH)
Frontend Standards
-
Component Structure:
- One component per file
- Use functional components with hooks
- Follow React best practices
-
TypeScript Usage:
- Strict mode enabled
- No 'any' types unless absolutely necessary
- Define interfaces for all props
-
Styling:
- Use TailwindCSS for styling
- Follow utility-first approach
- Maintain consistent spacing
-
State Management:
- Use React Context for global state
- Prefer hooks for local state
- Implement proper error boundaries
Backend Standards
-
API Design:
- RESTful principles
- Proper HTTP methods
- Consistent endpoint naming
- Version control in URL
-
Database:
- Use data annotations
- UTC timestamps
- Proper cascade rules
- Initialize collections
-
Security:
- HTTPS only
- JWT authentication
- Input validation
- XSS prevention
- CORS configuration
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.
- 1mo ago First seen · 213 lines · 1,168 tokens per session scan A 236a6036f449
project-rules is a cursor rule published in the GitHub repository Elumenotion/GuideAnts (61 stars, last pushed 2d ago), licensed Apache-2.0. It adds 1,168 tokens to every session, about $0.0047 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-30.
Other cursor rules, from other repositories
llm-router
When the user asks about architecture, system design, project structure, or "how should I build X", ALWAYS use the planworkflow MCP tool first.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
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.
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
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.