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 andregusman-raiz/a-gusman-claude --skill ag-otimizar-codigogit clone --depth 1 https://github.com/andregusman-raiz/a-gusman-claudeWrote 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/andregusman-raiz/a-gusman-claude/ag-otimizar-codigo)<a href="https://agentmods.dev/skills/andregusman-raiz/a-gusman-claude/ag-otimizar-codigo"><img src="https://agentmods.dev/badge/skills/andregusman-raiz/a-gusman-claude/ag-otimizar-codigo/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/andregusman-raiz/a-gusman-claude/ag-otimizar-codigo"><img src="https://agentmods.dev/badge/skills/andregusman-raiz/a-gusman-claude/ag-otimizar-codigo.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 4 Skill selects an external model or provider that may use a different account or billing plan than the operator expects. Undisclosed model switches can cause unexpected cost or quota consumption.Fix: Remove the model/provider override or disclose it prominently and require explicit operator approval before invoking an external coding CLI or billed model.
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.00035 | $0.01076 |
| Opus 5 | $0.00017 | $0.00538 |
| Sonnet 5 | $0.00007 | $0.00215 |
| Haiku 4.5 | $0.00003 | $0.00108 |
Grade A, and why
ag-otimizar-codigo 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 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
Prioridade: executar medicoes via CLI (lighthouse, bundle-analyzer, curl). How it starts
The opening of the file, as written. The whole thing — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ag-otimizar-codigo — Otimizar Codigo
Spawn the ag-otimizar-codigo agent to optimize code performance with before/after measurements.
Invocation
Use the Agent tool with:
subagent_type:ag-otimizar-codigomode:bypassPermissionsrun_in_background:trueprompt: Compose from template below + $ARGUMENTS
Prompt Template
Projeto: [CWD or user-provided path]
Area: [module or area to optimize from $ARGUMENTS]
Benchmark: [specific metric if provided, otherwise "auto-detect"]
## Output
- Metricas antes/depois: bundle size, render time, API latency, Lighthouse scores
- Relatorio de delta com melhorias documentadas
- Codigo otimizado com commits por otimizacao
Regra de ouro: "Otimizar sem medir e adivinhar."
1. Medir ANTES (bundle size, render time, API latency, Lighthouse, etc.)
2. Identificar gargalo
3. Otimizar
4. Medir DEPOIS
5. Comparar e reportar delta
Prioridade: executar medicoes via CLI (lighthouse, bundle-analyzer, curl).
Worktree isolation ativo.
Checklist explicito de otimizacao React/Next.js
Para projetos com React/Next, o agente DEVE verificar TODOS estes pontos antes de declarar otimizacao completa:
Re-renders desnecessarios
- Componentes que rerenderizam frequentemente sem mudanca de props → candidato a
React.memo - Funcoes inline em props (
onClick={() => ...}) → candidato auseCallback - Objetos/arrays inline em props (
style={{...}},data={[...]}) → candidato auseMemoou constante - Calculos custosos no render body → candidato a
useMemo
Listas e dados grandes
- Listas com > 200 itens sem virtualizacao → adicionar
react-windowou@tanstack/react-virtual - Tabelas grandes sem pagination + virtualization → considerar
@tanstack/react-table+ virtual -
.map()aninhado em arrays grandes (O(n*m)) → indexar via Map/Object lookup - Filtros/sorts no render (nao memoizados) → mover para
useMemo
Imagens e media
-
<img>nativo em projeto Next.js → migrar paranext/image(auto lazy + responsive + format) - Imagens sem
width/heightexplicitos → CLS (layout shift) - Imagens > 200KB sem compressao → otimizar via sharp ou Next.js Image Optimization
- Imagens above-the-fold sem
priority→ LCP ruim - Background images sem lazy → carregar tarde
- SVGs grandes nao otimizados → SVGO + considerar React component inline
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 · 96 lines · 35 tokens per session scan A 7541d0465922
ag-otimizar-codigo is a skill published in the GitHub repository andregusman-raiz/a-gusman-claude (19 stars, last pushed 4d ago), licensed MIT. It adds 35 tokens to every session and 1,076 once invoked, about $0.0002 per session on Opus 5. 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-09-03.
Other skills, from other repositories
docs-release-notes
Use when a change needs a user-visible release-note, changelog, or changeset entry — "add a release note", "add a changeset for this", "what goes in the changelog?", "write up what shipped", "note this for the next release" — or when finalizing a branch whose customer-visible features, bug fixes, or UI changes should…
swiftui-performance-audit
Audit and improve SwiftUI runtime performance. Use for requests to diagnose slow rendering, janky scrolling, high CPU/memory usage, excessive view updates, or layout thrash in SwiftUI apps.
extract-errors
Use when adding new error messages to React, or seeing "unknown error code" warnings.
cache-components
Expert guidance for Next.js Cache Components and Partial Prerendering (PPR). PROACTIVE ACTIVATION: Use this skill automatically when working in Next.js projects that have cacheComponents: true in their next.config.ts/next.config.js. When this config is detected, proactively apply Cache Components patterns and best…
manage-skills
A maintenance workflow for checking whether project verification skills still cover the code and rules that changed during a session.
systematic-debugging
Structured debugging methodology — use before proposing fixes for any error or failure. Covers: code bugs, build errors, deploy failures, config conflicts, dependency issues, infra problems. Also use when previous fix attempts failed or root cause is unclear.