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-preparar-ambientegit 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-preparar-ambiente)<a href="https://agentmods.dev/skills/andregusman-raiz/a-gusman-claude/ag-preparar-ambiente"><img src="https://agentmods.dev/badge/skills/andregusman-raiz/a-gusman-claude/ag-preparar-ambiente/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-preparar-ambiente"><img src="https://agentmods.dev/badge/skills/andregusman-raiz/a-gusman-claude/ag-preparar-ambiente.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to high
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 →
- high Privilege Escalation · line 83 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- 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.00038 | $0.01080 |
| Opus 5 | $0.00019 | $0.00540 |
| Sonnet 5 | $0.00008 | $0.00216 |
| Haiku 4.5 | $0.00004 | $0.00108 |
Grade A, and why
ag-preparar-ambiente 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 — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ambiente Detectado
- Docker: !
which docker 2>/dev/null && docker --version 2>/dev/null || echo "not installed" - Node: !
node --version 2>/dev/null || echo "not installed" - Python: !
python3 --version 2>/dev/null || echo "not installed"
ag-preparar-ambiente — Setup Ambiente
Quem você é
O Infraestrutor. Gera tudo que um dev precisa para rodar o projeto.
Modos
/ag-preparar-ambiente setup → Diagnóstico: o que falta?
/ag-preparar-ambiente docker → Dockerfile + docker-compose
/ag-preparar-ambiente ci → CI nativo (Vercel CI + husky), NÃO gera GHA por default
/ag-preparar-ambiente ci --gha-w[1-4] → SOMENTE se enquadrar whitelist gha-minimal.md
/ag-preparar-ambiente env → Auditar env vars
/ag-preparar-ambiente diagnosticar → Debug de pipeline quebrada
Regra GHA-mínimo (obrigatória no modo ci)
ANTES de gerar QUALQUER workflow, ler ~/Claude/.claude/rules/gha-minimal.md.
Default no modo ci:
- Gerar
.husky/pre-commitcomlint-stagedrodando typecheck + lint - Gerar
package.jsonscriptcheck:bun run typecheck && bun run lint && bun run test - Gerar
vercel.jsoncombuildCommand: "bun run check && bun run build" - NÃO gerar
.github/workflows/ci.yml
Workflow GHA SOMENTE se enquadrar W1-W4 (TOTVS/MSSQL legacy, CLI release multi-OS, VPS self-hosted, DB-first PR gate). Header obrigatório:
# JUSTIFICATIVA-GHA: <W1|W2|W3|W4> — <descrição>
# ALTERNATIVA-DESCARTADA: <opção nativa e razão>
O que gera
- Dockerfile multi-stage otimizado
- docker-compose com dev environment completo
- CI local-first:
.husky/pre-commit+vercel.json(Vercel CI cobre PR/deploy) - GHA workflow APENAS se whitelisted (W1-W4)
.env.exampledocumentado- Scripts de setup automatizados
Troubleshooting Comum
| Problema | Causa | Solucao |
|---|---|---|
| Docker build falha | Cache corrompido | docker system prune -a |
| Port already in use | Processo orfao | lsof -i :3000 / netstat -ano | findstr :3000 |
| npm install falha | Node version errada | Verificar .nvmrc ou engines no package.json |
| CI pipeline timeout | Build sem cache | Adicionar cache de node_modules e .next/cache |
| Env vars nao carregam | Arquivo errado | .env.local sobrescreve .env em Next.js |
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 · 38 tokens per session scan A 77c3f74f3f50
ag-preparar-ambiente is a skill published in the GitHub repository andregusman-raiz/a-gusman-claude (19 stars, last pushed 3d ago), licensed MIT. It adds 38 tokens to every session and 1,080 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
deployment-patterns
Deployment workflows, CI/CD pipeline patterns, Docker containerization, health checks, rollback strategies, and production readiness checklists for web applications. Use when setting up deployment infrastructure or planning releases.
scanning-containers-with-trivy-in-cicd
This skill covers integrating Aqua Security's Trivy scanner into CI/CD pipelines for comprehensive container image vulnerability detection. It addresses scanning Docker images for OS package and application dependency CVEs, detecting misconfigurations in Dockerfiles, scanning filesystem and git repositories, and…
scanning-docker-images-with-trivy
Trivy is a comprehensive open-source vulnerability scanner by Aqua Security that detects vulnerabilities in OS packages, language-specific dependencies, misconfigurations, secrets, and license violati.
implementing-aqua-security-for-container-scanning
Deploy Aqua Security's Trivy scanner to detect vulnerabilities, misconfigurations, secrets, and license issues in container images across CI/CD pipelines and registries.
deploy
Elixir/Phoenix deployment patterns — Dockerfile, fly.toml, runtime.exs, mix release, rel/ overlays. Use when configuring Fly.io, Docker, CI/CD, health checks, or production migrations.
performing-container-security-scanning-with-trivy
Scan container images, filesystems, and Kubernetes manifests for vulnerabilities, misconfigurations, exposed secrets, and license compliance issues using Aqua Security Trivy with SBOM generation and CI/CD integration.