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.
npx skills add parisgroup-ai/imersao-ia-setup --skill code-qualitygit clone --depth 1 https://github.com/parisgroup-ai/imersao-ia-setupWrote 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/skills/parisgroup-ai/imersao-ia-setup/code-quality)<a href="https://agentmods.dev/skills/parisgroup-ai/imersao-ia-setup/code-quality"><img src="https://agentmods.dev/badge/skills/parisgroup-ai/imersao-ia-setup/code-quality/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/skills/parisgroup-ai/imersao-ia-setup/code-quality"><img src="https://agentmods.dev/badge/skills/parisgroup-ai/imersao-ia-setup/code-quality.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.00082 | $0.02501 |
| Opus 5 | $0.00041 | $0.01251 |
| Sonnet 5 | $0.00016 | $0.00500 |
| Haiku 4.5 | $0.00008 | $0.00250 |
Grade A, and why
code-quality 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 9d 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 — 340 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Quality Skill
Esta skill mantém a saúde do código através de análise proativa e sob demanda. Detecta problemas, sugere consolidações e executa correções com aprovação.
Core Principle
Código limpo não é luxo, é necessidade. Débito técnico acumula juros.
┌─────────────────────────────────────────────────────────────┐
│ PROATIVO: Detectar durante desenvolvimento │
│ SOB DEMANDA: Análise profunda quando solicitado │
│ INTERATIVO: Sugerir e corrigir com aprovação │
└─────────────────────────────────────────────────────────────┘
Categorias de Análise
| Categoria | O que detecta | Severidade |
|---|---|---|
| 🪦 Código morto | Imports, variáveis, funções não usadas | Média |
| 🔄 Duplicação | Blocos similares, lógica repetida | Alta |
| 🧩 Consolidação | Componentes similares, padrões repetidos que virariam abstração | Alta |
| 🌀 Complexidade | Funções longas, aninhamento profundo, muitos parâmetros | Média |
| 🦨 Code smells | God classes, feature envy, primitive obsession | Alta |
| 🔗 Acoplamento | Dependências circulares, tight coupling | Alta |
Modos de Operação
Modo Proativo (Durante Desenvolvimento)
Ativado automaticamente. Alerta ao detectar problemas em qualquer arquivo visível.
1. Claude trabalhando em arquivo
│
▼
2. Detecta problema em arquivo atual OU relacionado
│
▼
3. Severidade Alta? ──Não──▶ Anota para relatório final
│
Sim
│
▼
4. Alerta inline:
"⚠️ Detectei [problema] em [arquivo:linha].
Quer que eu analise/corrija agora ou depois?"
Gatilhos proativos:
| Problema | Threshold para alertar |
|---|---|
| Código morto óbvio | Import/variável não usada no arquivo atual |
| Duplicação | Bloco > 10 linhas duplicado |
| Consolidação | 3+ componentes/funções similares detectados |
| Complexidade | Função > 50 linhas ou aninhamento > 4 |
| Code smell | God class, feature envy detectado |
| Acoplamento | Dependência circular criada |
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.
- 9d ago First seen · 340 lines · 82 tokens per session scan A 6a37ffba51f1
code-quality is a skill published in the GitHub repository parisgroup-ai/imersao-ia-setup (1 stars, last pushed 27d ago), licensed MIT. It adds 82 tokens to every session and 2,501 once invoked, about $0.0004 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-31.
Other skills, from other repositories
clean-code-detect-smells
This skill should be used when the user asks to "find code smells", "review code quality", mentions "code smells", "technical debt", discusses identifying problematic code patterns, or wants a systematic code quality assessment.
architecture-optimization
Guided journey from a working codebase grown slow and tangled to one measurably fast, cleanly bounded, and readable. Orchestrates eight skills phase by phase - working-with-legacy-code, clean-architecture, software-design-philosophy, refactoring-patterns, system-design, ddia-systems, release-it, pragmatic-programmer …
improve-code-quality
Guided journey from a working-but-untested vibe-coded prototype to a production-ready product with tests, clean structure, a business-rules boundary, and resilience at scale. Orchestrates nine skills phase by phase - working-with-legacy-code, clean-code, refactoring-patterns, software-design-philosophy…
remove-technical-debt
Guided journey from a large aged codebase everyone fears to touch to one that is safe to change, legible, bounded, and resilient - paid down in place without a rewrite. Orchestrates eight skills phase by phase - working-with-legacy-code, refactoring-patterns, clean-code, software-design-philosophy, clean-architecture…
refactoring-patterns
Apply named refactoring transformations to improve code structure without changing behavior. Use when the user mentions "refactor this", "code smells", "extract method", "replace conditional", "technical debt", "move method", "inline variable", "decompose conditional", or "clean up this messy code". Also trigger when…
release-it
Build production-ready systems with stability patterns: circuit breakers, bulkheads, timeouts, and retry logic. Use when the user mentions "production outage", "circuit breaker", "deployment pipeline", "chaos engineering", "retry storm", "health checks", "my service keeps crashing", "prevent cascading failures", or…