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/Joaonic/agentkitWrote 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/joaonic/agentkit/25-clean-code)<a href="https://agentmods.dev/rules/joaonic/agentkit/25-clean-code"><img src="https://agentmods.dev/badge/rules/joaonic/agentkit/25-clean-code/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/joaonic/agentkit/25-clean-code"><img src="https://agentmods.dev/badge/rules/joaonic/agentkit/25-clean-code.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.00745 |
| Opus 5.5 | $0.00000 | $0.00298 |
| Sonnet 5.5 | $0.00000 | $0.00149 |
| Haiku 4.5 | $0.00000 | $0.00075 |
Grade A, and why
25-clean-code 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.
How it starts
The opening of the file, as written. The whole thing — 52 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Clean Code
Single Responsibility e Abstrações
- SRP: Uma classe/função = uma responsabilidade clara. Se o nome precisar de "e" ou "ou", considere extrair.
- OCP: Preferir abstrações para extensão sem alterar código existente. Não criar abstrações que não resolvem problema real.
- Quando extrair: mesma lógica em 2+ lugares; ou módulo/classe faz mais de uma coisa distinta.
Complexidade e Legibilidade
- Complexidade Ciclomática Máxima: Funções/métodos devem ter complexidade ciclomática ≤ 10. Se exceder, refature extraindo funções menores.
- Complexidade Cognitiva: Evite aninhamento excessivo; use early returns; extraia funções para lógica complexa.
- Early returns (Guard clauses): Coloque validações e null-checks no topo; mantenha o caminho feliz linear e ao final.
- Código Auto-Explicativo: O código deve ser auto-explicativo através de nomes descritivos. Comentário inline para explicar "o quê" = código mal escrito.
Condicionais por Tipo e Enums
- Evitar cadeias de
if/elseouswitchpor tipo: quando houver 3+ ramos baseados em tipo de domínio, prefiraMap/objeto indexado por enum. - Sempre usar enum, nunca string literal: magic strings de domínio SEMPRE substituídas por enums/constantes tipadas.
- Switch com ≤ 2 casos: aceitável manter
if/elsesimples, desde que enum seja usado.
Comentários e Documentação
- EVITE comentários inline: o código deve ser auto-explicativo por nomes e estrutura.
- Comentários permitidos apenas para:
- Javadoc/JSDoc/TSDoc em APIs públicas (classes, métodos/funções exportados, componentes, hooks).
- Decisões de design não óbvias ou trade-offs arquiteturais.
- Restrições ou contexto que o código não pode expressar.
- Código comentado = código morto: use git para histórico; remova código comentado.
- Nomenclatura Descritiva: prefira nomes longos e descritivos a nomes curtos com comentários.
Limpeza de Passagem
- Ao modificar um arquivo: faça limpeza necessária sem alterar API pública e sem quebrar testes.
- Durante limpeza: remova comentários desnecessários, melhore nomes pouco descritivos, reduza complexidade, remova código morto, elimine imports não usados.
- DRY: não repita lógica. Extraia para funções/utilitários/classes reutilizáveis.
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 · 52 lines · 0 tokens per session scan A a2ac4015e76e
25-clean-code is a cursor rule published in the GitHub repository Joaonic/agentkit (2 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 745 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-31.
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.
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
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.
config-validation-and-normalization
Config validation and normalization responsibilities (defineConfig normalizes, the orm section schema validates and resolves paths, the loader reports per-section diagnostics).