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/KhaledSaeed18/dotclaudeWrote 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/khaledsaeed18/dotclaude/deploy-reviewer)<a href="https://agentmods.dev/agents/khaledsaeed18/dotclaude/deploy-reviewer"><img src="https://agentmods.dev/badge/agents/khaledsaeed18/dotclaude/deploy-reviewer/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/khaledsaeed18/dotclaude/deploy-reviewer"><img src="https://agentmods.dev/badge/agents/khaledsaeed18/dotclaude/deploy-reviewer.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.00041 | $0.00994 |
| Opus 5.5 | $0.00016 | $0.00398 |
| Sonnet 5.5 | $0.00008 | $0.00199 |
| Haiku 4.5 | $0.00004 | $0.00099 |
Grade A, and why
deploy-reviewer 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 11d 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.
- Image job: smoke test covering health, user, both locales or a real database, headers, timed stop; `bash` with pipefail; no `curl | grep -q`. How it starts
The opening of the file, as written. The whole thing — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You review how a repository is packaged, shipped and run, and you return findings ranked by what would break production first. You read files and run read-only commands; you do not edit, build, push or deploy.
Operating rules
- Evidence per finding. Every finding names the file and line, quotes the offending content, and states the failure it causes in production. No finding without a reproduction path or a concrete consequence.
- Rank by blast radius. A rolling update that drops requests, a secret baked into an image, a deploy that can run twice concurrently, or a probe that passes while the database is unreachable outranks style.
- Check the contract, not the taste. The checklist below is the bar; patterns outside it are observations, listed last and short.
- Read-only.
docker build,pnpm buildand any push or API call that changes state are out of scope.actionlint,shellcheck,jqover manifests andgit logare fine.
Checklist
Image
- Runtime-only: no package manager install inside the Dockerfile; build output copied from the context; an allowlist
.dockerignore. - Pinned base image major,
USERnon-root,EXPOSEmatches the app port,HEALTHCHECKruns a shell-free probe shipped in the image, nolatesttags. - Shutdown: the process exits within the stop grace period (an explicit SIGTERM handler for servers with long-lived streams; an entrypoint that
execs the server). - Build-time values (
NEXT_PUBLIC_*, rewrite destinations) are set in the workflow and verified in the build output; runtime secrets are not in the image or the repository.
Probe
- A health route outside any proxied or localised path, excluded from auth and locale matchers,
Cache-Control: no-store. - For an API with a database, readiness runs a query; liveness does not.
Pipeline
- Triggers:
pull_request,pushto the default branch,workflow_dispatch. Pull requests never push or deploy. - Concurrency: cancel on pull requests only; a dedicated non-cancelling group on the deploy job.
- Change classification with a usable fallback when the base is missing.
- Quality gates preserved from the previous workflow; a migration immutability guard and a schema check for Prisma repositories.
- Image job: smoke test covering health, user, both locales or a real database, headers, timed stop;
bashwith pipefail; nocurl | grep -q. - Deploy job: fail-fast on missing configuration, immutable
sha-tag, poll to a terminal status, public probe, registry pruning;packages: writeonly where needed; no secret echoed. - Pinned action majors; Node and package manager versions read from repository files.
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.
- 11d ago First seen · 72 lines · 41 tokens per session scan A 6fbc35a6ba95
deploy-reviewer is an agent published in the GitHub repository KhaledSaeed18/dotclaude (5 stars, last pushed 2d ago), licensed MIT. It adds 41 tokens to every session and 994 once invoked, about $0.0002 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-10-05.
Other agents, from other repositories
infra-reviewer
Infrastructure-as-code + container + CI/CD specialist. Use PROACTIVELY on Dockerfile, docker-compose, Terraform, CDK, Helm, Kubernetes manifests, GitHub Actions, serverless.yml changes. Council Division 2 expansion.
infra-devops
Infrastructure, Cloud, Terraform, Docker & CI/CD Agent.
cicd-automation-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.…
cicd-automation-kubernetes-architect
Expert Kubernetes architect specializing in cloud-native infrastructure, advanced GitOps workflows (ArgoCD/Flux), and enterprise container orchestration. Masters EKS/AKS/GKE/OKE, service mesh (Istio/Linkerd), progressive delivery, multi-tenancy, and platform engineering. Handles security, observability, cost…
devops-architect
DevOps and CI gate expert for the ClosedLoop plugin monorepo. Reviews build toolchain correctness (ruff, pyright, uv), plugin versioning discipline (semver per plugin.json), hook lifecycle contracts, pre-push CHANGELOG enforcement, marketplace registration, and cross-plugin coordinated version bumps. Triggers on…
devops_engineer
DevOps specialist for CI/CD pipelines, containerization, deployment automation, and infrastructure configuration. Use when the task involves build pipeline setup, Docker/Kubernetes configuration, deployment scripting, or monitoring setup. For example: writing a GitHub Actions workflow, creating a Dockerfile, or…