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/extending-ui)<a href="https://agentmods.dev/rules/elumenotion/guideants/extending-ui"><img src="https://agentmods.dev/badge/rules/elumenotion/guideants/extending-ui/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/extending-ui"><img src="https://agentmods.dev/badge/rules/elumenotion/guideants/extending-ui.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.00000 | $0.02607 |
| Opus 5.5 | $0.00000 | $0.01043 |
| Sonnet 5.5 | $0.00000 | $0.00521 |
| Haiku 4.5 | $0.00000 | $0.00261 |
Grade A, and why
extending-ui 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 — 365 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Rules for Extending UI Features with Backend Changes
1. Analysis Phase
1.1 Feature Scope Assessment
- Identify the specific UI components that need to be added/modified
- Determine what data needs to be persisted or retrieved
- Map out any new user interactions or workflows
- Identify affected existing components and potential side effects
1.2 Data Model Impact
- Check if existing entities can support the new feature
- If new data is needed, determine if it requires:
- New entity
- Extension of existing entity
- New relationships
- New computed properties
- Verify cascade delete implications
- Consider data migration needs
1.3 API Requirements
- List required CRUD operations
- Identify new DTOs needed
- Map authentication/authorization requirements
- Consider rate limiting needs
- Plan API versioning impact
2. Implementation Order
2.1 Data Layer Changes
- Add/modify entity classes in
GuideAntsApi.DataModel - Configure relationships in
ApplicationDbContext - Create migration using
dotnet ef migrations - Verify migration SQL for unexpected changes
- Update any affected repository methods
2.2 API Layer Changes
- Create/update DTOs in
GuideAntsApi/Models - Add/modify service interfaces and implementations
- Configure new endpoints in appropriate endpoint class
- Add authorization requirements
- Implement validation
2.3 Frontend Changes
- Add new types/interfaces in TypeScript
- Create/update API client methods
- Implement UI components
- Add state management code
- Implement error handling
- Add loading states
3. Required Files to Modify
3.1 Backend Files
GuideAntsApi.DataModel/
Models/ # Add/modify entity classes
ApplicationDbContext.cs # Configure relationships
GuideAntsApi/
Models/ # Add DTOs
Services/ # Add/modify services
Endpoints/ # Add endpoint configurations
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 · 365 lines · 0 tokens per session scan A 16771b5bf62c
extending-ui is a cursor rule published in the GitHub repository Elumenotion/GuideAnts (61 stars, last pushed yesterday), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 2,607 tokens. 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
api-endpoints
Rules for NestJS controllers, services, and DTOs in apps/api.
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.