Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/varienos/agentic-workflownpx agentmods add commands/varienos/agentic-workflow/pre-deploy.skeletonWrote 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/varienos/agentic-workflow/pre-deploy.skeleton)<a href="https://agentmods.dev/commands/varienos/agentic-workflow/pre-deploy.skeleton"><img src="https://agentmods.dev/badge/commands/varienos/agentic-workflow/pre-deploy.skeleton/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/commands/varienos/agentic-workflow/pre-deploy.skeleton"><img src="https://agentmods.dev/badge/commands/varienos/agentic-workflow/pre-deploy.skeleton.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.00000 | $0.03302 |
| Opus 5.5 | $0.00000 | $0.01321 |
| Sonnet 5.5 | $0.00000 | $0.00660 |
| Haiku 4.5 | $0.00000 | $0.00330 |
Grade C, and why
pre-deploy.skeleton scanned grade C 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 24d 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.
Harvests environment variableshighData exfiltration
Enumerating or grepping the environment for keys collects credentials unrelated to what the mod says it does.
# Extract environment variables from docker-compose.prod.yml How it starts
The opening of the file, as written. The whole thing — 354 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pre-Deploy — Coolify Production Push Check
Runs all pre-deployment checks for Coolify production and presents the test report.
Usage:
/pre-deploy
Rule: Work Autonomously
- Run all checks in sequence.
- Do not push; this command only checks.
- If an error occurs, report it; do not ask the user mid-flow.
- Complete every step — do not skip a step.
Step 1 — Initial Check (Git Status + Branch)
cd ../Codebase && git status && git branch --show-current && git log --oneline -1
Check:
- Are there uncommitted changes?
- Which branch are you on? (WARN if not main/master — Coolify usually auto-deploys on main push)
- In sync with remote? (check "ahead/behind" in
git statusoutput)
If there are uncommitted changes:
FAIL: Uncommitted changes exist. Commit first.
If the branch is not main/master:
WARN: You are on '{branch}'. Coolify auto-deploy is usually triggered by a push to main.
Step 2 — Summary of Changes Since Last Deployment
List changes made since the last deployment:
cd ../Codebase && git log --oneline HEAD~20..HEAD
Categorize:
- New Features (feat:)
- Bug Fixes (fix:)
- Breaking Changes (commits containing breaking change)
- Database Migrations (commits containing migration)
- Infrastructure Updates (Dockerfile, docker-compose, entrypoint.sh, CI/CD)
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.
- 24d ago Changed · +2 lines scan A → C 2053627681d6
- 1mo ago First seen · 352 lines · 0 tokens per session scan A 97b76a6eb819
pre-deploy.skeleton is a command published in the GitHub repository varienos/agentic-workflow (59 stars, last pushed 24d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 3,302 tokens. A static security scan graded it C with 1 finding (harvests environment variables). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
mlops
Invoke the MLOps Engineer for model serving & inference infrastructure, ML/AI pipelines, model deployment & monitoring, and infrastructure-level AI cost optimization.
devops
Invoke the DevOps Engineer for cloud infrastructure, IaC (Terraform/OpenTofu), Kubernetes, CI/CD pipelines, containers, and deployment.
review
A command for reviewing code with security checks and a check for compliance with MX tags. The available description does not explain what MX tags are.
pr-enhance
Command "pr-enhance" from ruvnet/ruflo, covering pr-enhance, usage, options, examples and enhance pr.
gh-security-review
Use to perform a dedicated security review of current branch changes before pushing.
btp-architecture-review
Review SAP BTP architecture decisions for account model, services, security, integration, operations, and rollout readiness.