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/post-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/post-deploy.skeleton)<a href="https://agentmods.dev/commands/varienos/agentic-workflow/post-deploy.skeleton"><img src="https://agentmods.dev/badge/commands/varienos/agentic-workflow/post-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/post-deploy.skeleton"><img src="https://agentmods.dev/badge/commands/varienos/agentic-workflow/post-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.02848 |
| Opus 5.5 | $0.00000 | $0.01139 |
| Sonnet 5.5 | $0.00000 | $0.00570 |
| Haiku 4.5 | $0.00000 | $0.00285 |
Grade D, and why
post-deploy.skeleton scanned grade D with 3 findings 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 25d 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.
Hidden instructionshighPrompt injection
Directives inside HTML comments, invisible characters or bidirectional overrides are read by the model and not by the person reviewing the file.
<!-- GENERATE: SMOKE_TEST_ENDPOINTS Explanation: This section is populated by Bootstrap using manifest data. Required manifest fields: environments, api_endpoints, project.api_prefix Example output: ## Smoke Test Endpoin Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
cat > ../.claude/reports/deploys/deploy-$(date '+%Y%m%d-%H%M%S').md << 'DEPLOY_EOF' Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -sf --max-time 10 https://api.example.com/health | jq . How it starts
The opening of the file, as written. The whole thing — 318 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Post-Deploy — Coolify Deploy Validation
Coolify from user-side validates the production environment's stability after deployment. Usage:
/post-deploy
Invariant Rule: Automation Test
- Perform sequential tests on all controls — do not change anything.
- Do not modify any element — only test and report.
- Execute all steps — complete one step.
- If rollback is required, follow instructions — do not attempt to make changes yourself.
Step 1 — Deployment Wait Period
Wait for the Coolify build + deployment process to complete:
echo "Waiting for the Coolify build and deploy (90 seconds)..." && sleep 90
NOT: The build duration changes based on the project. Typical times:
- Simple Node.js application: 30-60 seconds
- Multi-stage Docker build: 60-120 seconds
- Monorepo build: 90-180 seconds
You can control whether the build has completed by checking Coolify dashboard.
Step 2 — Health Check
Check the health status of your production environment.
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.
- 25d ago Changed · -54 lines b272480b07c6
- 1mo ago First seen · 372 lines · 0 tokens per session scan D 8213ee4466cd
post-deploy.skeleton is a command published in the GitHub repository varienos/agentic-workflow (59 stars, last pushed 25d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,848 tokens. A static security scan graded it D with 3 findings (hidden instructions, reads agent configuration directories, makes network calls). 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.
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.
fe
Invoke Frontend Developer for React, TypeScript, Next.js, and React Native development.
rev
Invoke Code Reviewer for code quality, security, requirements validation, and best practices review.