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-analisar-contextogit 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-analisar-contexto)<a href="https://agentmods.dev/skills/andregusman-raiz/a-gusman-claude/ag-analisar-contexto"><img src="https://agentmods.dev/badge/skills/andregusman-raiz/a-gusman-claude/ag-analisar-contexto/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-analisar-contexto"><img src="https://agentmods.dev/badge/skills/andregusman-raiz/a-gusman-claude/ag-analisar-contexto.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.00048 | $0.00698 |
| Opus 5.5 | $0.00019 | $0.00279 |
| Sonnet 5.5 | $0.00010 | $0.00140 |
| Haiku 4.5 | $0.00005 | $0.00070 |
Grade A, and why
ag-analisar-contexto 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 2mo 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 — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ag-analisar-contexto — Analisar Contexto
Spawn the ag-analisar-contexto agent to diagnose code patterns, tech debt, and architectural risks.
Invocation
Use the Agent tool with:
subagent_type:ag-analisar-contextomode:autorun_in_background:trueprompt: Compose from template below + $ARGUMENTS
Prompt Template
Projeto: [CWD or user-provided path]
Analisar o codebase produzindo diagnostico com prioridades P0-P3:
- Consistencia de padroes
- Debito tecnico (TODOs, any, magic numbers)
- Riscos arquiteturais (acoplamento, single points of failure)
- Cobertura de testes
- Seguranca superficial
Salvar incrementalmente em docs/ai-state/findings.md.
Important
- ALWAYS spawn as Agent subagent — do NOT execute inline
- After spawning, confirm to the user that the agent is running in background
- Requires ag-explorar-codigo output (project-profile.json, codebase-map.md) for best results
Output
- findings.md em docs/ai-state/ com prioridades P0-P3
- Inventario de tech debt: TODOs, tipos
any, magic numbers, duplicacao, deps desatualizadas - Riscos arquiteturais: single points of failure, dependencias circulares, gaps de seguranca
Anti-Patterns
- NUNCA diagnosticar sem ler codigo — findings do ag-explorar-codigo sao ponto de partida, nao substituto
- NUNCA classificar tudo como P0 — se tudo e critico, nada e critico; usar P0-P3 rigorosamente
- NUNCA misturar diagnostico com prescricao — diagnostico e ag-analisar-contexto, solucao e ag-especificar-solucao
Escalacao: Issues para Tech Debt P0
Findings P0 (blocking production) DEVEM ser registrados como GitHub Issues:
Agent({
subagent_type: "ag-registrar-issue",
name: "issue-registrar",
model: "haiku",
run_in_background: true,
prompt: "Repo: [detectar]\nOrigem: ag-analisar-contexto\nSeveridade: P0-critical\nTitulo: [Tech Debt] descricao do problema\nContexto: [descricao completa, impacto, arquivos afetados, risco se nao resolvido]\nArquivos: [arquivos afetados]\nLabels: tech-debt"
})
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.
- 2mo ago First seen · 74 lines · 48 tokens per session scan A 86f384fbdc36
ag-analisar-contexto is a skill published in the GitHub repository andregusman-raiz/a-gusman-claude (18 stars, last pushed 1mo ago), licensed MIT. It adds 48 tokens to every session and 698 once invoked, about $0.0002 per session on Opus 5.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
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
cwv-optimizer
Diagnose and fix Core Web Vitals issues on AEM Edge Delivery Services pages. Goes deeper than generic CWV advice by understanding EDS-specific performance patterns including the 100KB LCP budget, E-L-D loading phases, block rendering behavior, and third-party script impact. Produces specific fixes for LCP, CLS, and…
incident-response-incident-response
Coordinate production incident triage, mitigation, investigation, recovery, and follow-up. Use when responding to outages or other incidents that require structured operational coordination.
ci-fixer
CI failures - read error, minimal fix, verify.