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 agentmods add agents/zapprosite/claude-code-minimax/deploy-checkgit clone --depth 1 https://github.com/zapprosite/claude-code-minimaxWhat 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 | $0.00021 | $0.00689 |
| Opus 5 | $0.00010 | $0.00345 |
| Sonnet 5 | $0.00004 | $0.00138 |
| Haiku 4.5 | $0.00002 | $0.00069 |
Grade B, and why
deploy-check scanned grade B with 2 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 2d 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
sudo zfs snapshot -r "$SNAPSHOT" Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- Bash(curl *coolify*) What it actually says
Deploy Check Agent
Executa validação completa antes de qualquer deploy ou mudança em produção.
Preflight Checklist
Executar nesta ordem:
1. Snapshot ZFS (se aplicável)
# Criar snapshot antes de mudança
SNAPSHOT="tank@pre-$(date +%Y%m%d-%H%M%S)-deploy"
sudo zfs snapshot -r "$SNAPSHOT"
echo "Snapshot created: $SNAPSHOT"
2. Health Check Serviços
# Docker services
docker ps --format "table {{.Names}}\t{{.Status}}"
# Health endpoints
curl -s http://localhost:6333/health || echo "Qdrant: FAIL"
curl -s http://localhost:5678/api/v1/health || echo "n8n: FAIL"
curl -s http://localhost:8000/api/v1/health || echo "Coolify: FAIL"
3. Verificar Espaço em Disco
df -h /srv
df -h /home/will
4. Verificar ZFS Pool
zpool status tank
zfs list tank
5. Rollback Plan Documented
# Documentar como rollback
echo "ROLLBACK: sudo zfs rollback -r $SNAPSHOT"
Decision Matrix
| Condição | Ação |
|---|---|
| Todos serviços healthy | ✅ Pode prosseguir |
| 1-2 serviços down | ⚠️ Verificar se são críticos — prosseguir com cautela |
| 3+ serviços down | ❌ PARAR — investigar antes |
| Disco >90% | ❌ PARAR — liberar espaço antes |
| ZFS pool degraded | ❌ PARAR — resilver antes |
Output
## 🚀 Deploy Check — $(date '+%Y-%m-%d %H:%M')
### ✅ Preflight
- [x] Snapshot criado: <snapshot>
- [x] Serviços: <N>/<total> healthy
- [x] Disco: <uso>
- [x] ZFS pool: <status>
### 📋 Rollback Plan
sudo zfs rollback -r
### 🟢 Resultado
**APTO PARA DEPLOY**
// ou //
### 🔴 Resultado
**BLOQUEADO** — <razão>
Gatilho
Invocar via /agent deploy-check quando:
- Antes de
docker compose up -d --pull - Antes de upgrade de serviço
- Antes de mudanças em configuração de rede
- Após qualquer ação em
/srv/data
Limitações
- Não substitui testes automatizados
- Não valida funcionamento da aplicação pós-deploy
- Assume que health endpoints são confiáveis
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.
- 2d ago First seen · 113 lines · 21 tokens per session scan B 39720435b465
deploy-check is an agent published in the GitHub repository zapprosite/claude-code-minimax (2 stars, last pushed 4mo ago), licensed MIT. It adds 21 tokens to every session and 689 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it B with 2 findings (asks for root, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.