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/madebyaris/rakitui-aiWrote 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/madebyaris/rakitui-ai/web-development)<a href="https://agentmods.dev/rules/madebyaris/rakitui-ai/web-development"><img src="https://agentmods.dev/badge/rules/madebyaris/rakitui-ai/web-development/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/madebyaris/rakitui-ai/web-development"><img src="https://agentmods.dev/badge/rules/madebyaris/rakitui-ai/web-development.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.00000 | $0.03876 |
| Opus 5.5 | $0.00000 | $0.01550 |
| Sonnet 5.5 | $0.00000 | $0.00775 |
| Haiku 4.5 | $0.00000 | $0.00388 |
Grade A, and why
web-development scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
const data = await fetch(url, { How it starts
The opening of the file, as written. The whole thing — 729 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Web Development Patterns
Modern web development best practices for JavaScript, TypeScript, and related frameworks.
CRITICAL: Project Setup Workflow
ALWAYS Use CLI Tools for New Projects
WRONG approach (creates incomplete/broken projects):
1. Create package.json manually
2. Create files one by one
3. Copy component code from documentation
4. Forget to run npm install
CORRECT approach:
# Next.js
npx create-next-app@latest my-app --typescript --tailwind --app --eslint
# React (Vite)
npm create vite@latest my-app -- --template react-ts
# Vue
npm create vue@latest
# Then for component libraries:
cd my-app
npx shadcn-ui@latest init
npx shadcn-ui@latest add button card dialog
Version Checking Before Setup
<think>
Before creating a project, I MUST:
1. Check current stable versions
2. Verify CLI options are up to date
3. Check for compatibility issues
</think>
→ web_search("create-next-app latest version options December 2024")
→ web_search("shadcn-ui Next.js 15 compatibility 2024")
JavaScript Best Practices
Modern Syntax
- Use
constby default,letwhen reassignment needed, nevervar - Prefer arrow functions for callbacks and short functions
- Use template literals for string interpolation
- Destructure objects and arrays
- Use spread operator for immutable operations
// Modern patterns
const { name, email } = user;
const updatedList = [...items, newItem];
const greeting = `Hello, ${name}!`;
const fetchData = async () => { /* ... */ };
Async Patterns
- Prefer
async/awaitover.then()chains - Always handle errors with try/catch
- Use
Promise.all()for parallel operations - Use
Promise.allSettled()when some failures are acceptable
// Parallel operations
const [users, posts] = await Promise.all([
fetchUsers(),
fetchPosts()
]);
// Error handling
try {
const data = await fetchData();
} catch (error) {
console.error('Fetch failed:', error.message);
throw new DataFetchError(error);
}
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 · 729 lines · 0 tokens per session scan A 3e2eec806354
web-development is a cursor rule published in the GitHub repository madebyaris/rakitui-ai (5 stars, last pushed 8mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 3,876 tokens. A static security scan graded it A with 1 finding (makes network calls). 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
AIRules
NexusLink MCP four-step workflow and prohibitions (copy to project .cursor/rules/ and fill the project-specific section).
002-verify-before-act
Requires Claude to read before writing, verify before installing, and confirm before destructive operations.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
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.
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.