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/Thanhdeptr/K8s_AI_Assistant_MCPWrote 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/thanhdeptr/k8s_ai_assistant_mcp/react)<a href="https://agentmods.dev/rules/thanhdeptr/k8s_ai_assistant_mcp/react"><img src="https://agentmods.dev/badge/rules/thanhdeptr/k8s_ai_assistant_mcp/react/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/thanhdeptr/k8s_ai_assistant_mcp/react"><img src="https://agentmods.dev/badge/rules/thanhdeptr/k8s_ai_assistant_mcp/react.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.00804 | $0.00804 |
| Opus 5.5 | $0.00322 | $0.00322 |
| Sonnet 5.5 | $0.00161 | $0.00161 |
| Haiku 4.5 | $0.00080 | $0.00080 |
Grade A, and why
react 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- reactvite-rules — 95% identical, 3 lines differ
What it actually says
React + Vite Project Standards
Overview
- Framework: React + Vite
- Routing: React Router DOM
- API Layer: Supabase JavaScript Client (docs)
- Styling: Tailwind CSS as primary, CSS Modules only for custom overrides
Directory Structure
src/ ├── components/ │ ├── layout/ # Shared layout components │ ├── pages/ # Feature-based pages │ │ ├── home/ # Home page │ │ ├── user/ # User management │ │ └── [feature]/ # Additional modules ├── services/ # API services for each module │ ├── user.ts # User API services │ └── [feature].ts # Feature-specific APIs ├── assets/ # Static assets (images, fonts, icons) ├── styles/ # Global and scoped CSS │ ├── globals.css # Global Tailwind config │ ├── [page].module.css # Page-specific custom styles ├── App.tsx # Root App component ├── main.tsx # Vite entry point └── env.d.ts # Type definitions for env variables
Naming Conventions
- Components: PascalCase → UserDetail.tsx
- Service files: camelCase → userApi.ts
- CSS Modules: kebab-case → user-detail.module.css
- Directories: lowercase → user, product
- Hooks: start with use → useUserData.ts
Feature Implementation Workflow
Add a New Module
- Create a new folder under src/components/pages/[feature]/
- Add API service in src/services/[feature].ts
- Add custom CSS in src/styles/[feature].module.css (if needed)
Add a New Page to Existing Module
- Add component file: src/components/pages/[module]/[page].tsx
- Add optional CSS: src/styles/[module]-[page].module.css
- Add route in App.tsx
Add Shared Component
- Place in src/components/common/ with reusable logic
Add New API
- Extend the existing service file for the module
- Return typed responses and handle errors gracefully
Styling Guidelines
- Tailwind First: Use utility classes for 90% of styling
- Scoped Styles: Use CSS Modules only when Tailwind cannot cover edge cases
- Avoid Global Overrides: Keep globals.css minimal
- Responsive Design: Mobile-first using Tailwind breakpoints
Page Template
`tsx import { useState, useEffect } from 'react' import { getUserData } from '@/services/user'
export function UserListPage() { const [users, setUsers] = useState([]) const [isLoading, setIsLoading] = useState(true)
useEffect(() => { fetchData() }, [])
async function fetchData() { try { const data = await getUserData() setUsers(data) } catch (error) { console.error('Failed to fetch users:', error) } finally { setIsLoading(false) } }
if (isLoading) return Loading...
return (
User List
{users.map(user => ( {user.name}
))}
) } `
Service API Example
`ts import { supabase } from '@/lib/supabase' import type { User } from '@/types/user'
export async function getUserData(): Promise { const { data, error } = await supabase.from('users').select('*') if (error) throw new Error(Supabase Error: ${error.message}) return data || [] } `
Database Interaction
- Use supabase-js client strictly per official docs
- All services return typed results and handle errors upfront
Tools Used
- Supabase: For database queries
- Playwright: For browser automation and previews
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 · 157 lines · 804 tokens per session scan A f929004cfcfe
react is a cursor rule published in the GitHub repository Thanhdeptr/K8s_AI_Assistant_MCP (0 stars, last pushed 1y ago), licensed MIT. It adds 804 tokens to every session, about $0.0032 per session on Opus 5.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-08-31.
Other cursor rules, from other repositories
windsurfrules
Create detailed components with these requirements.
state-management
Use the following stack. Do not introduce or recommend Redux or React Context for shared/global state.
backend
Backend development rules for TT Studio - AI model management backend.
tanstack-start-guide
TanStack Start best practices emphasizing client-first architecture, type safety, and modern React patterns.
new-component
Workflow for creating new React components.
tanstack-react-router_routing
TanStack Router: Routing.