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-corrigir-tiposgit 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-corrigir-tipos)<a href="https://agentmods.dev/skills/andregusman-raiz/a-gusman-claude/ag-corrigir-tipos"><img src="https://agentmods.dev/badge/skills/andregusman-raiz/a-gusman-claude/ag-corrigir-tipos/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-corrigir-tipos"><img src="https://agentmods.dev/badge/skills/andregusman-raiz/a-gusman-claude/ag-corrigir-tipos.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.00060 | $0.01695 |
| Opus 5 | $0.00030 | $0.00847 |
| Sonnet 5 | $0.00012 | $0.00339 |
| Haiku 4.5 | $0.00006 | $0.00169 |
Grade A, and why
ag-corrigir-tipos 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 13d 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 — 150 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ag-corrigir-tipos — Fix TypeScript
Spawn the ag-corrigir-tipos agent to handle TypeScript error correction — from diagnosis to large-scale sweeps.
Auto-Routing
The agent auto-selects the best mode based on input:
| Input | Mode | Behavior |
|---|---|---|
| "diagnosticar tipos" / desconhecido | --scan |
Categorizar erros, gerar plano (read-only) |
| 1-10 erros claros | --fix |
Batch incremental, 5 arquivos/batch, commits |
| 10-50 erros | --fix |
Multiplos batches com quality gates |
| 50+ erros / "limpar tipos" | --sweep |
Varredura por categoria, ratchet threshold |
| "audit any" / "scan any" / "props sem tipo" | --audit-any |
Auditoria proativa SEM precisar de erro TS |
| Pos-upgrade de lib | ag-depurar-erro first | Causa raiz, depois --fix |
Invocation
Use the Agent tool with:
subagent_type:ag-corrigir-tiposmode:bypassPermissionsrun_in_background:true(except--fix< 10 errors which runs foreground)prompt: Compose from template below + $ARGUMENTS
Prompt Template
Projeto: [CWD or user-provided path]
Modo: [--scan|--fix|--sweep] (ou auto-detect)
Escopo: [all | modulo | lista de arquivos]
Threshold CI: [numero, se aplicavel para ratchet]
Executar correcao de erros TypeScript no modo indicado (ou auto-detect).
Seguir quality gates: max 5 arquivos/batch, commit entre batches, zero `as any`.
Important
- ALWAYS spawn as Agent subagent — do NOT execute inline
- After spawning, confirm to the user
- For
--scan: agent is READ-ONLY, does NOT fix errors - For
--fix: commits incrementally every 5 files - For
--sweep: categorizes first, then attacks by type (easy→hard) - For
--audit-any: READ-ONLY, audita codigo SEM depender de erros TS emitidos - NEVER uses
as any,@ts-ignore, or relaxesstrictmode - Memory safety: max 1
tscprocess, uses LSP for quick checks
Modo --audit-any (auditoria proativa de qualidade de tipos)
Audita o codigo SEM precisar de erros TS emitidos pelo tsc. Detecta 4 problemas que strict mode nao captura sozinho:
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.
- 13d ago First seen · 150 lines · 60 tokens per session scan A 55818c45eb26
ag-corrigir-tipos is a skill published in the GitHub repository andregusman-raiz/a-gusman-claude (19 stars, last pushed 4d ago), licensed MIT. It adds 60 tokens to every session and 1,695 once invoked, about $0.0003 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 skills, from other repositories
javascript-sandbox
Best practices for using the clodex built-in JavaScript sandbox for browser debugging, fetched-data processing, attachments, and mini-app orchestration within its bundled capability boundary.
async-await-patterns
Use when writing JavaScript or TypeScript code with asynchronous operations, fixing promise-related bugs, or converting callback/promise patterns to async/await. Triggers: 'promise chain', 'unhandled rejection', 'race condition in JS', 'callback hell', 'Promise.all', 'sequential vs parallel async', 'missing await'.…
react-component-development
Component patterns and best practices for React with TypeScript. Covers functional components, custom hooks, state management, composition patterns, error boundaries, server components, and form handling. Keywords: React component, hooks, state management, TypeScript component, custom hooks, Zustand, useReducer…
pmd
Set up, run, and triage PMD static analysis on a Maven/Java project — the ruleset, the plugin wiring, parsing the report by rule and priority, copy-paste detection, and how to suppress a finding at the right level. Use when the user says "run PMD", "PMD is failing", "fix the PMD violations", "add static analysis"…
build-error-resolver
Build and TypeScript error resolution specialist. Use PROACTIVELY when build fails or type errors occur.
mk:typescript
Use when writing TypeScript code, fixing type errors, or configuring strict type safety. Auto-activates on .ts/.tsx files. Covers null handling, utility types, and ESLint.