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-creation-guidegit 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.00331 |
| Opus 5 | $0.00000 | $0.00166 |
| Sonnet 5 | $0.00000 | $0.00066 |
| Haiku 4.5 | $0.00000 | $0.00033 |
Grade A, and why
api-creation-guide 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 yesterday.
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 Creation Guide following MVVM architecture and Material3" globs: "" alwaysApply: true
API Creation Guide Rules
Overview
This rule provides guidelines for adding API call logic based on API documentation following MVVM architecture and Material3 guidelines. Reference the detailed guide from CreateAPIGuide.md.
Requirements
API Call Function
- Write API call functions that match the API documentation
- Follow the rules specified in
Create API and UI Binding Guide
Constraints
- Imports: Check existing versions and use appropriate import statements
- Responsiveness: Code must be responsive
- API Documentation: Required for implementation
Expected Results
API Interface
- API functions added to appropriate API interface
- Explore existing API interfaces and add functions to appropriate locations
- Avoid creating new interfaces when possible
ViewModel Integration
- API call functions exist in appropriate ViewModel
- Avoid creating new ViewModels when possible
- Reuse existing ViewModels that handle similar functionality
Flow Implementation
- Add flows that match API documentation
- Use
Anytype for responses when specific response handling is not needed - Follow existing patterns in the codebase
Implementation Guidelines
- Ensure all implementations are consistent with existing project patterns and rules
- Follow MVVM architecture and Material3 guidelines
- Maintain code consistency and readability
- Use proper error handling and loading states
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.
- yesterday First seen · 50 lines · 0 tokens per session scan A d83989311a12
api-creation-guide is a cursor rule published in the GitHub repository HeeGyeong/ComposeSample (11 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 331 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
cursorrules
Kortix is a React Native + Expo app built with TypeScript, NativeWind (Tailwind CSS), and a custom design system.
git-commit-attribution
Git commits must use the human developer identity only; never Cursor Agent co-authorship.
android-viewmodel
Android ViewModel conventions — StateFlow, repository abstraction, coroutines, no LiveData.
ios-ui-development-focus
UI/UX and SwiftUI best practices - HIG compliance, presentation APIs, layout patterns.
react_hooks
React Hooks best practices for frontend package.
swift
Swift patterns: SwiftUI, actors, async/await, value types.