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/yu-iskw/llmops-demo-tsWrote 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/yu-iskw/llmops-demo-ts/vue-rules)<a href="https://agentmods.dev/rules/yu-iskw/llmops-demo-ts/vue-rules"><img src="https://agentmods.dev/badge/rules/yu-iskw/llmops-demo-ts/vue-rules.svg" alt="Measured on agentmods" 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.02071 | $0.02071 |
| Opus 5 | $0.01035 | $0.01035 |
| Sonnet 5 | $0.00414 | $0.00414 |
| Haiku 4.5 | $0.00207 | $0.00207 |
Grade A, and why
vue-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 3d 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 — 177 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Vue.js Development Guidelines
You are an expert in JavaScript, TypeScript, and the Vue.js framework for scalable web development.
Key Principles
- Write concise, technical responses with accurate Vue.js examples.
- Leverage Vue.js reactivity system effectively.
- Prioritize performance optimization and minimal JavaScript for optimal user experience.
- Use descriptive variable names and follow Vue.js naming conventions.
- Organize files logically, typically by feature or component type.
Project Structure
- Use the recommended Vue CLI or Vite project structure.
- Organize components into
components/for reusable UI elements. - Organize views/pages into
views/orpages/for route-specific components. - Organize utility files into
utils/orhelpers/. - Organize state management related files into
store/orstores/.
Recommended Modular Project Structure
For larger and more complex Vue.js applications, a modular monolithic architecture is highly recommended. This approach encapsulates each feature or domain, enhancing maintainability and scalability.
src/
├── app.ts # Main application setup (Express, middleware, error handlers)
├── main.ts # Main entry point for Vue application
├── router.ts # Global Vue Router configuration
├── store.ts # Global Pinia/Vuex store configuration
├── assets/ # Static assets like images, fonts, global styles
│ └── images/
│ └── styles/
├── core/ # Common components, services, and utilities used across the application
│ ├── components/ # Base or common UI components (e.g., BaseButton.vue)
│ ├── models/ # Core TypeScript interfaces/types for global entities
│ ├── store/ # Global or shared Pinia/Vuex modules
│ ├── services/ # Common business logic services
│ ├── views/ # Common layout components (e.g., DefaultLayout.vue)
│ └── utils/ # Common utility functions
├── modules/ # Feature-specific modules, each self-contained
│ ├── checkout/ # Example feature module (e.g., for e-commerce checkout)
│ │ ├── components/ # Components specific to the checkout module
│ │ ├── models/ # TypeScript interfaces/types for checkout entities
│ │ ├── store/ # Pinia/Vuex store specific to checkout
│ │ ├── services/ # Business logic services for checkout
│ │ ├── views/ # Routed components (pages) for checkout
│ │ └── routes.ts # Route definitions for the checkout module
│ ├── user/ # Example user management module
│ │ ├── components/
│ │ ├── models/
│ │ ├── store/
│ │ ├── services/
│ │ ├── views/
│ │ └── routes.ts
│ └── ...
├── plugins/ # Vue plugins
├── types/ # Custom global type definitions
├── tests/ # Unit and integration tests
└── scss/ # Global SCSS files
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.
- 3d ago First seen · 177 lines · 2,071 tokens per session scan A c431d18a7670
vue-rules is a cursor rule published in the GitHub repository yu-iskw/llmops-demo-ts (6 stars, last pushed 6d ago), licensed Apache-2.0. It adds 2,071 tokens to every session, about $0.0104 per session on Opus 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-09-04.
Other cursor rules, from other repositories
vue3-typescript-auto
Vue 3 with TypeScript Standards.
page_layer_rules
Page layer rules for Next.js App Router pages and layouts.
type_layer_rules
Type layer rules for TypeScript type definitions and interfaces.
vue-typescript-patterns
A set of coding rules for Vue 3 projects using TypeScript, a language that adds type checking to JavaScript. It covers component structure, file locations, TypeScript usage, and Pinia, a library for shared application state.
sveltekit-tailwindcss-typescript-cursorrules-promp
Cursor rules for SvelteKit development with Tailwind CSS and TypeScript integration.
project-overview
A project overview for a uni-app application built with Vue 3, TypeScript, Vite, and UnoCSS. It explains the supported platforms, main folders, configuration files, and development commands.