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/tecnomanu/agent-rules-kitWrote 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/tecnomanu/agent-rules-kit/00-project-overview)<a href="https://agentmods.dev/rules/tecnomanu/agent-rules-kit/00-project-overview"><img src="https://agentmods.dev/badge/rules/tecnomanu/agent-rules-kit/00-project-overview.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.00352 | $0.00352 |
| Opus 5 | $0.00176 | $0.00176 |
| Sonnet 5 | $0.00070 | $0.00070 |
| Haiku 4.5 | $0.00035 | $0.00035 |
Grade A, and why
00-project-overview 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 7d 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.
What it actually says
Project Overview & Guidelines
This repository contains agent‑rules‑kit, a CLI tool and template set that bootstraps Cursor rules for multiple stacks. The rules in this folder govern the maintenance of this very project.
| Topic | Quick rule |
|---|---|
| CLI changes | Update code in cli/services/ modules and cli/index.js; add unit and integration tests. |
| Templates | Follow folder layout: templates/global/, templates/stacks/<stack>/base/, templates/stacks/<stack>/architectures/, templates/stacks/<stack>/v*/. |
| Config | Keep templates/kit-config.json as single source of truth for globs, version ranges & default architectures. |
| Releases | Bump package.json + CHANGELOG. Tag using vx.y.z. |
| Language | All code, documentation, and files must be written in English, even if communicating with the agent in another language. |
Language Policy
While you may interact with the agent in any language, all project files, code, comments, documentation, and rules must be written in English. This ensures consistency and maintainability across the project. When working with the Agent Rules Kit:
- Write all code, comments, and docstrings in English
- Create documentation files in English
- Use English for variable names, function names, and other identifiers
- Use English for commit messages and pull requests
- Keep configuration files in English
For example, if you're communicating with the agent in Spanish, the agent should respond in Spanish, but any generated or modified code must still be in English.
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.
- 7d ago First seen · 30 lines · 352 tokens per session scan A 52c237d96fbe
00-project-overview is a cursor rule published in the GitHub repository tecnomanu/agent-rules-kit (35 stars, last pushed 11mo ago), licensed ISC. It adds 352 tokens to every session, about $0.0018 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-08-30.
Other cursor rules, from other repositories
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.
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.