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.
git clone --depth 1 https://github.com/christopherlouet/claude-baseWrote 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/agents/christopherlouet/claude-base/ops-deploy)<a href="https://agentmods.dev/agents/christopherlouet/claude-base/ops-deploy"><img src="https://agentmods.dev/badge/agents/christopherlouet/claude-base/ops-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/agents/christopherlouet/claude-base/ops-deploy"><img src="https://agentmods.dev/badge/agents/christopherlouet/claude-base/ops-deploy.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00029 | $0.00557 |
| Opus 5.5 | $0.00012 | $0.00223 |
| Sonnet 5.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 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.
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.
- 1mo 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 4d ago), licensed MIT. It adds 29 tokens to every session and 557 once invoked, about $0.0001 per session on Opus 5.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
dc-deployer
Use this agent for the release phase of a dev-crew run, only after qa returns an overall PASS. Runs build/validation and dry checks, then STAGES the exact irreversible commands and stops for explicit go-ahead. Never auto-executes a deploy.
release-changelog-composer
Compose the prose of one release cut from the records that shipped in it — the changelog lines and the release page, every line and headline citing the record id it reports, so the binary can prove both documents describe exactly the cut. Host-delegated; feeds abcd launch ship --changelog-json.
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.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.