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-pipeline-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-pipeline-deploy)<a href="https://agentmods.dev/skills/andregusman-raiz/a-gusman-claude/ag-pipeline-deploy"><img src="https://agentmods.dev/badge/skills/andregusman-raiz/a-gusman-claude/ag-pipeline-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-pipeline-deploy"><img src="https://agentmods.dev/badge/skills/andregusman-raiz/a-gusman-claude/ag-pipeline-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.00049 | $0.00841 |
| Opus 5.5 | $0.00020 | $0.00336 |
| Sonnet 5.5 | $0.00010 | $0.00168 |
| Haiku 4.5 | $0.00005 | $0.00084 |
Grade A, and why
ag-pipeline-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 1mo 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 — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ag-pipeline-deploy — Deploy Pipeline
Spawn the ag-pipeline-deploy agent to run the full 8-stage deploy pipeline autonomously with auto-recovery.
Invocation
Use the Agent tool with:
subagent_type:ag-pipeline-deploymode:bypassPermissionsrun_in_background:trueprompt: Compose from template below + $ARGUMENTS
Prompt Template
Projeto: [CWD or user-provided path]
Ambiente: [preview|production]
## Output
- Pipeline 8-stage report: env check → typecheck → lint → test → build → deploy → smoke → final
- Status por etapa (PASS/FAIL/RECOVERED)
- Auto-recovery attempts documentados (max 3 por stage)
Execute o pipeline completo end-to-end:
1. Env check 2. Typecheck 3. Lint 4. Test 5. Build 6. Deploy 7. Smoke test 8. Report
Auto-recovery em cada etapa (max 3 tentativas). Se falha apos 3 tentativas, reportar e parar.
Caminho padrao: PR-based via Vercel Git Integration (pre-deploy-gate.sh no buildCommand). Pipeline manual para repos sem Git Integration.
Important
- ALWAYS spawn as Agent subagent — do NOT execute inline
- Runs in background with fork context (autonomous pipeline)
- After spawning, confirm to the user
Troubleshooting
| Erro | Causa Comum | Solucao |
|---|---|---|
| Build OOM | Bundle grande, memory limit | NODE_OPTIONS='--max-old-space-size=8192' |
| Typecheck timeout | Projeto grande sem incremental | bunx tsc --noEmit --incremental |
| Flaky tests | Race conditions, network deps | --retry=2 ou @flaky tag + skip |
| Missing secrets | Env vars nao configuradas | vercel env ls ou gh secret list |
| Deploy stuck | Vercel queue, rate limit | vercel ls → verificar status |
| Smoke test 404 | Rota nao gerada, rewrite rules | Verificar vercel.json rewrites |
| Build cache stale | Cache corrompido | vercel --force ou limpar .next/ |
| ESLint new errors | Dep update trouxe novas regras | --max-warnings=N temporario |
Recovery Procedures
Build OOM
export NODE_OPTIONS='--max-old-space-size=8192'
bun run build
# Se persistir: analisar bundle com `bunx next build --analyze`
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.
- 1mo ago First seen · 81 lines · 49 tokens per session scan A c3865abd079a
ag-pipeline-deploy is a skill published in the GitHub repository andregusman-raiz/a-gusman-claude (18 stars, last pushed 1mo ago), licensed MIT. It adds 49 tokens to every session and 841 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-09-03.
Other skills, from other repositories
chinese-git-workflow
A reference for configuring Git with Chinese code-hosting services such as Gitee, Coding.net, GitLab China, and CNB, including SSH, HTTPS, credentials, CI, and repository mirroring.
atmos-profiles
Atmos profiles: profile directories, --profile and ATMOSPROFILE activation, profile merge behavior, environment switching, and routing profile-specific auth/toolchain/config overrides.
webhook-management
Configure and validate CCAM webhook targets across supported chat, incident, automation, and generic providers. Use when listing provider requirements, creating or updating a target, scoping it to alert rules, sending a test notification, reviewing delivery history, or deleting a target.
managing-github-actions-secrets
Creates and updates GitHub Actions secrets for PostHog workflows. Use when adding a new CI secret, rotating an existing secret, wiring a workflow to an API token, package registry credential, deploy key, or any value referenced via ${{ secrets. }} in .github/workflows/.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.
deployment-engineer
Expert deployment engineer specializing in modern CI/CD pipelines, GitOps workflows, and advanced deployment automation. Masters GitHub Actions, ArgoCD/Flux, progressive delivery, container security, and platform engineering. Handles zero-downtime deployments, security scanning, and developer experience optimization.…