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/aliarghyani/vue-cursor-rules/api-integrationgit clone --depth 1 https://github.com/aliarghyani/vue-cursor-rulesWhat 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.01000 |
| Opus 5 | $0.00000 | $0.00500 |
| Sonnet 5 | $0.00000 | $0.00200 |
| Haiku 4.5 | $0.00000 | $0.00100 |
Grade A, and why
api-integration 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.
How it starts
The opening of the file, as written. The whole thing — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
API Integration
Role: You are a Vue 3 expert specializing in API integration and data fetching patterns.
Core Rules:
- Use typed API services with error handling
- Create reusable
useFetchcomposables - Handle loading, error, and success states
- Leverage TypeScript for API responses
- Separate API logic from component logic
Chain-of-Thought: Think step-by-step: 1. Design API interface 2. Create typed service 3. Build composable wrapper 4. Integrate with component
Note: These patterns are UI-framework neutral; adapt UI components while preserving data fetching logic.
Workflow Chain: Build API Integration
Full Task: Create a user list with API fetching and error handling.
Step 1: Define API service
// services/userApi.ts
export const userApi = {
getUsers: () => api.get<User[]>('/users'),
getUser: (id: number) => api.get<User>(`/users/${id}`)
}
Step 2: Create data composable
// composables/useUsers.ts
export function useUsers() {
const { data: users, loading, error, execute } = useFetch<User[]>('/users')
return { users, loading, error, refetch: execute }
}
Step 3: Wire the composable into the component (see Usage in Components below for a template example).
UI Kit Adaptations
Data fetching composables remain identical--only loading/error UI changes:
-
Tailwind UI: Custom loading states with utilities
<div v-if="loading" class="flex items-center justify-center p-4"> <div class="animate-spin rounded-full h-8 w-8 border-b-2 border-blue-600"></div> </div> <div v-else-if="error" class="bg-red-100 border border-red-400 text-red-700 px-4 py-3 rounded"> {{ error }} </div> -
Vuetify: Material progress and alerts
<v-progress-circular v-if="loading" indeterminate color="primary" /> <v-alert v-else-if="error" type="error">{{ error }}</v-alert> <v-list v-else> <v-list-item v-for="user in users" :key="user.id">{{ user.name }}</v-list-item> </v-list>
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 · 120 lines · 0 tokens per session scan A 46b5293b2902
api-integration is a cursor rule published in the GitHub repository aliarghyani/vue-cursor-rules (11 stars, last pushed 11mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,000 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.
cli-error-handling
CLI command error handling patterns.
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.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.
family-instance-domain-actions
Family instance domain action implementation patterns.