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/heegyeong/composesample/api-ui-bindinggit clone --depth 1 https://github.com/HeeGyeong/ComposeSampleWhat 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.00000 | $0.00433 |
| Opus 5 | $0.00000 | $0.00217 |
| Sonnet 5 | $0.00000 | $0.00087 |
| Haiku 4.5 | $0.00000 | $0.00043 |
Grade A, and why
api-ui-binding 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
description: "API and UI Binding Creation using MVVM and Material3" globs: "" alwaysApply: true
API and UI Binding Creation Rules
Overview
This rule explains the steps to add APIs using MVVM architecture and connect data to UI following Material3 guidelines. Reference the detailed guide from CreateAPIAndUIBindingGuide.md.
Requirements
1. DTO Creation
- Generate DTOs that match API documentation
- Follow data class implementation rules from DataRules.md
2. API Interface
- Add API call functions within already declared API interfaces
- Create new interfaces only when no appropriate existing interface exists
- Use proper naming and organization
3. API Call Function Implementation
- Implement API call functions that match API documentation
- Use proper HTTP methods and endpoints
- Include error handling and response processing
4. ViewModel Integration
- Add API call functions to appropriate ViewModel
- Store data through API calls via ViewModel
- Render UI with stored data
- Follow ViewModel patterns from DIRules.md
Constraints
- Import: Use import statements after checking existing versions
- Responsiveness: Ensure code responsiveness
Expected Results
API Interface
- API functions added to API interface
ViewModel
- API call functions exist in appropriate ViewModel
- Data stored after API calls
UI Rendering
- UI rendered with stored data
- Follow UI guidelines from UIRules.md
Additional Guidelines
- Follow MVVM architecture and Material3 guidelines
- Implement according to existing project patterns and rules
- Maintain consistency across the codebase
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 · 60 lines · 0 tokens per session scan A 7b519d930886
api-ui-binding is a cursor rule published in the GitHub repository HeeGyeong/ComposeSample (11 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 433 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
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.
coolify-ai-docs
Master reference to all Coolify AI documentation in .ai/ directory.
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.
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.