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 commands/dimitrigeelen/agentic-engineering-framework/deploy-checkgit clone --depth 1 https://github.com/DimitriGeelen/agentic-engineering-frameworkWrote 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/commands/dimitrigeelen/agentic-engineering-framework/deploy-check)<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="Measured on agentmods" 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 | $0.00000 | $0.00646 |
| Opus 5 | $0.00000 | $0.00323 |
| Sonnet 5 | $0.00000 | $0.00129 |
| Haiku 4.5 | $0.00000 | $0.00065 |
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 today.
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 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:
- Read
.context/working/focus.yaml— checkcurrent_taskis set - If no task is set, STOP and say: "No active task. Run
/start-workfirst."
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:
Dockerfiledeploy/docker-compose.swarm.ymldeploy/traefik-routes.yml.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:
- Push to trigger CI/CD:
git push - Tag for production:
git tag vX.Y.Z && git push --tags - Manual scaffold:
fw deploy scaffold --app watchtower
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.
- today First seen · 85 lines · 0 tokens per session scan A c9b738960e74
deploy-check is a command published in the GitHub repository DimitriGeelen/agentic-engineering-framework (13 stars, last pushed today), 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.
Other commands, from other repositories
service-check
Request each agent to run a self-diagnostic to validate their runtime setup.
compatibility-audit
Audit all agents for Trinity compatibility by requesting self-diagnostics from each agent.
request-research
Ask the researcher to investigate a specific topic.
health
Perform a health check on all agents and identify any issues.
restart-all
Restart all agents in the fleet. Use with caution!
schedules
Quick overview of all schedules across the platform.