agentic-engineering-framework: Command for Claude Code

.claude/commands/deploy-check.md

deploy-check is a command for Claude Code from DimitriGeelen/agentic-engineering-framework. It costs 0 tokens per session (646 once invoked), scanned A, original, Apache-2.0.

A pre-deployment checklist command that checks for an active task, runs an audit, tests access to a Docker registry and an Ollama model server, and verifies required deployment files. Deployment means making software available to run in an environment.

In plain words
What is it for?
Use it before deployment to validate Docker-related infrastructure, the model server connection, registry access, and files such as the Dockerfile and compose configuration.
Why use it?
It catches missing work context, failed audits, unreachable services, and missing files before a deployment is triggered. It also distinguishes warnings from failures that block deployment.

Command for Claude Code

Written for Claude Code: installed under .claude/.

This is DimitriGeelen/agentic-engineering-framework's own configuration. It tells Claude Code how to work on agentic-engineering-framework itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything agentic-engineering-framework configures →

Reuse

Borrowing it

Nothing to install: this file belongs to DimitriGeelen/agentic-engineering-framework. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/DimitriGeelen/agentic-engineering-framework/master/.claude/commands/deploy-check.md
Clone the repo
git clone --depth 1 https://github.com/DimitriGeelen/agentic-engineering-framework

Made for: Claude Code.

Wrote 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.

agentmods badge for deploy-check

README.md
[![agentmods](https://agentmods.dev/badge/commands/dimitrigeelen/agentic-engineering-framework/deploy-check/github.svg)](https://agentmods.dev/commands/dimitrigeelen/agentic-engineering-framework/deploy-check)
Your own site
<a href="https://agentmods.dev/commands/dimitrigeelen/agentic-engineering-framework/deploy-check"><img src="https://agentmods.dev/badge/commands/dimitrigeelen/agentic-engineering-framework/deploy-check/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.

agentmods 80×15 button for deploy-check

Your own site · 80×15
<a href="https://agentmods.dev/commands/dimitrigeelen/agentic-engineering-framework/deploy-check"><img src="https://agentmods.dev/badge/commands/dimitrigeelen/agentic-engineering-framework/deploy-check.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 646 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.00646
Opus 5.5 $0.00000 $0.00258
Sonnet 5.5 $0.00000 $0.00129
Haiku 4.5 $0.00000 $0.00065

Measured 1mo ago against content hash c9b738960e74, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

deploy-check 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.

curl -sf http://192.168.10.201:5000/v2/_catalog | head -5
.claude/commands/deploy-check.md · 85 lines

How it starts

The opening of the file, as written. The whole thing — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/deploy-check - Pre-Deployment Validation

Run this before triggering a deployment to verify all prerequisites are met.

Step 1: Task Gate

Verify an active task exists:

  1. Read .context/working/focus.yaml — check current_task is set
  2. If no task is set, STOP and say: "No active task. Run /start-work first."

Step 2: Run Pre-Deploy Audit

fw audit --section deployment

Capture the exit code:

  • Exit 0: All gates passed
  • Exit 1: Warnings (deployment can proceed with caution)
  • Exit 2: Failures (deployment blocked — must fix first)

Step 3: Check Registry Reachability

curl -sf http://192.168.10.201:5000/v2/_catalog | head -5

If unreachable, report: "Docker registry at 192.168.10.201:5000 is unreachable."

Step 4: Check Ollama Reachability from App Host

curl -sf http://192.168.10.107:11434/api/tags | head -5

If unreachable, report: "Ollama GPU host at 192.168.10.107:11434 is unreachable — containers won't be able to run Q&A."

Step 5: Verify Deployment Files Exist

Check these files exist in the project root:

  1. Dockerfile
  2. deploy/docker-compose.swarm.yml
  3. deploy/traefik-routes.yml
  4. .onedev-buildspec.yml

Step 6: Check Local Health Endpoint

If the app is running locally:

curl -sf http://localhost:3000/health

Report the health status (app, ollama, embeddings).

Step 7: Present Results

Present a numbered checklist:

## Deploy Readiness Check

1. [PASS/FAIL] Active task: T-XXX
2. [PASS/FAIL] Pre-deploy audit (fw audit --section deployment)
3. [PASS/FAIL] Docker registry reachable (192.168.10.201:5000)
4. [PASS/FAIL] Ollama GPU host reachable (192.168.10.107:11434)
5. [PASS/FAIL] Deployment files present
6. [PASS/FAIL] Local health endpoint

Result: READY / NOT READY (N issues to fix)

If NOT READY, list remediation steps for each failure.

If READY, suggest next steps:

  1. Push to trigger CI/CD: git push
  2. Tag for production: git tag vX.Y.Z && git push --tags
  3. Manual scaffold: fw deploy scaffold --app watchtower

Read the full file on GitHub · 85 lines

Changes

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.

  1. 1mo ago First seen · 85 lines · 0 tokens per session scan A c9b738960e74

Subscribe to this mod's changes

deploy-check is a command published in the GitHub repository DimitriGeelen/agentic-engineering-framework (18 stars, last pushed yesterday), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 646 tokens. 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-09-04.