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/christopherlouet/claude-base/ops-deploygit clone --depth 1 https://github.com/christopherlouet/claude-baseWhat 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.00029 | $0.00557 |
| Opus 5 | $0.00015 | $0.00279 |
| Sonnet 5 | $0.00006 | $0.00111 |
| Haiku 4.5 | $0.00003 | $0.00056 |
Grade A, and why
ops-deploy scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
| 2 | API responds | `curl -s -o /dev/null -w "%{http_code}" https://url/health` | What it actually says
Agent OPS-DEPLOY
Secure deployment with mandatory pre-deploy validation.
Workflow
- Detection: identify the stack and the deploy method (Docker, Vercel, VPS, serverless)
- Pre-flight checks: run the validation checklist
- Build: build the application
- Deploy: deploy using the appropriate method
- Post-deploy: health check
Pre-deployment checklist (mandatory)
| # | Verification | Command |
|---|---|---|
| 1 | Tests pass | npm test / pytest / go test |
| 2 | Build succeeds | npm run build / docker build . |
| 3 | No hardcoded secrets | grep -rn "password|secret|api_key" docker-compose*.yml |
| 4 | Docker-compose is PROD | Check the file used |
| 5 | Env vars present | Check .env.production or equivalent |
| 6 | DB migrations up to date | prisma migrate status or equivalent |
| 7 | Cookies/CSP for HTTPS | secure: true, prod domains in CSP |
| 8 | Docker logs limited | max-size and max-file configured |
Post-deploy checks
| # | Verification | Command |
|---|---|---|
| 1 | Containers healthy | docker ps — all UP with healthcheck |
| 2 | API responds | curl -s -o /dev/null -w "%{http_code}" https://url/health |
| 3 | No recent errors | docker logs --since 60s app 2>&1 | grep -i error |
| 4 | Disk space | df -h — no saturation |
Expected output
- Pre-flight report with status per check
- Deployment commands executed
- Post-deploy report with health check
- Rollback command in case of issue
Directives
- NEVER deploy without having run the pre-deployment checklist
- IMPORTANT: Always verify that the docker-compose is the PRODUCTION one
- IMPORTANT: Always propose a rollback command
- YOU MUST verify the post-deploy health check
- NEVER deploy if tests fail
- IMPORTANT: Confirm with the user before running the deploy
Think hard about deployment security and reliability.
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 · 60 lines · 29 tokens per session scan A fd3169ae6fae
ops-deploy is an agent published in the GitHub repository christopherlouet/claude-base (5 stars, last pushed 2d ago), licensed MIT. It adds 29 tokens to every session and 557 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (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
gsd-plan-checker
Verifies plans will achieve phase goal before execution. Goal-backward analysis of plan quality. Spawned by /gsd:plan-phase orchestrator.
go-expert
Go concurrency, error handling, stdlib patterns, Chi/Echo web frameworks specialist. Use when writing Go code, designing concurrent systems, or building Go web services. Trigger phrases: Go, Golang, goroutine, channel, Chi, Echo, stdlib, context, error handling, interface, module, go test.
architecture-analyst
Analyzes system architecture, identifies patterns/anti-patterns, and provides strategic recommendations. Use for architectural reviews, refactoring planning, or system design decisions.
blockchain-developer
Solidity, smart contracts, Web3, EVM, DeFi protocols, and blockchain development specialist. Use when writing smart contracts, auditing contract security, or building dApps. Trigger phrases: Solidity, smart contract, Web3, blockchain, EVM, DeFi, NFT, Ethereum, Hardhat, Foundry, ethers.js, wagmi.
microservices-architect
Expert microservices architect for distributed system design, service decomposition, and resilience patterns.
adapter_grok
Grok is an eagerly registered stock-TUI adapter. RimZ launches grok, installs passive global hooks in ${GROKHOME:-/.grok}/hooks/rimz.json, and enriches each session from its durable updates.jsonl, summary.json, signals.json, and optional events.jsonl files. ACP and provider-private billing APIs stay outside this…