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-publicar-deploygit 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-publicar-deploy)<a href="https://agentmods.dev/skills/andregusman-raiz/a-gusman-claude/ag-publicar-deploy"><img src="https://agentmods.dev/badge/skills/andregusman-raiz/a-gusman-claude/ag-publicar-deploy/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-publicar-deploy"><img src="https://agentmods.dev/badge/skills/andregusman-raiz/a-gusman-claude/ag-publicar-deploy.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.00033 | $0.00501 |
| Opus 5 | $0.00016 | $0.00251 |
| Sonnet 5 | $0.00007 | $0.00100 |
| Haiku 4.5 | $0.00003 | $0.00050 |
Grade A, and why
ag-publicar-deploy 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.
What it actually says
ag-publicar-deploy — Publicar Deploy
Spawn the ag-publicar-deploy agent to deploy code to preview, production, or rollback.
Invocation
Use the Agent tool with:
subagent_type:ag-publicar-deploymode:autorun_in_background:falseprompt: Compose from template below + $ARGUMENTS
Prompt Template
Projeto: [CWD]
Ambiente: [preview|production|rollback]
URL: [URL de producao, se conhecida]
Execute o deploy seguindo o protocolo de seguranca: preflight checks, deploy, smoke tests.
Caminho padrao para producao: PR merge em master -> Vercel Git Integration (pre-deploy-gate.sh no buildCommand).
NUNCA usar vercel --prod direto sem pipeline.
Important
- ALWAYS spawn as Agent subagent — do NOT execute inline
- After spawning, confirm to the user
Output
- Deploy executado no ambiente solicitado (preview ou producao)
- Smoke test results com URL de acesso
- Rollback executado se necessario, com estado anterior restaurado
- Verificacao: CI verde, deploy sucesso, metricas estaveis, logs limpos
Anti-Patterns
- NUNCA deploy com testes falhando — "passa local" nao conta; smoke tests em staging devem passar
- NUNCA deploy sem smoke test pos-deploy — metricas estaveis? Logs sem erro? Response time aceitavel?
- NUNCA deploy sem plano de rollback — antes de apertar botao: como reverter em 2 min?
- NUNCA deploy com PRs pendentes — PR pendente pode conter fix de producao; mergear antes
- NUNCA ignorar alertas do provider — "preview failed" e sinal; nao forcar producao se preview esta red
Quality Gate
- Smoke tests passam apos deploy?
- Logs sem erros novos?
- Metricas estaveis (latency, error rate)?
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 · 58 lines · 33 tokens per session scan A 9ebc50040006
ag-publicar-deploy is a skill published in the GitHub repository andregusman-raiz/a-gusman-claude (19 stars, last pushed 3d ago), licensed MIT. It adds 33 tokens to every session and 501 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
control-plane-ops
Operar o control-plane local-first do agents-lab com board canônico, long-runs bounded, handoff/checkpoint, rollout/rollback e espelhos externos sem perder governança.
deploy-docs
Validate and prepare documentation for GitHub Pages deployment.
gcp-setup
Automates Google Cloud Console setup via browser. Use when the user wants to set up a GCP project, enable APIs, create service accounts, configure IAM, set up billing, configure OAuth, set up firewall rules, or deploy to Cloud Run/App Engine/GKE. Also use when the user says "set up GCP", "configure Google Cloud"…
cloudflare-connect
Adds a subdomain to a Cloudflare-managed zone and wires it to a hosting platform (Railway, Vercel) via browser automation. Use when the user wants to point a subdomain at a Railway service, Vercel project, or other hosting platform. Also use when the user says "add a subdomain", "connect domain to Railway/Vercel"…
assh
Use when SSH, remote commands, logs, file transfer, deploy, or server inspection is needed — bootstraps connections, manages tmux sessions, keeps output out of agent context.
cost-analysis
Analyzes infrastructure costs at 1K-100K user scales by reading the actual codebase, auto-detecting cloud providers, modeling per-action costs, and projecting total monthly spend with optimization recommendations.