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/bybren-llc/safe-agentic-workflownpx agentmods add commands/bybren-llc/safe-agentic-workflow/rollback-devWrote 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/bybren-llc/safe-agentic-workflow/rollback-dev)<a href="https://agentmods.dev/commands/bybren-llc/safe-agentic-workflow/rollback-dev"><img src="https://agentmods.dev/badge/commands/bybren-llc/safe-agentic-workflow/rollback-dev/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/bybren-llc/safe-agentic-workflow/rollback-dev"><img src="https://agentmods.dev/badge/commands/bybren-llc/safe-agentic-workflow/rollback-dev.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.00011 | $0.02057 |
| Opus 5.5 | $0.00004 | $0.00823 |
| Sonnet 5.5 | $0.00002 | $0.00411 |
| Haiku 4.5 | $0.00001 | $0.00206 |
Grade C, and why
rollback-dev scanned grade C with 2 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 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.
Reaches for credential fileshighPrivilege escalation
SSH keys, cloud credentials, git-credentials, .npmrc, /etc/shadow: reading these is how a config file becomes a credential leak.
| `{{SSH_KEY_PATH}}` | Path to SSH private key | `~/.ssh/id_ed25519_staging` | Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s http://{{REMOTE_HOST}}:3000/api/health 2>/dev/null || echo "Health check failed" This is a copy
86% identical to remote-rollback — 122 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 273 lines — stays where its author put it; the contents beside it link to each section on GitHub.
📋 TEMPLATE: This command is a template. See "Customization Guide" below to adapt for your infrastructure.
Rollback the {{DEV_MACHINE}} dev environment to a previous Docker image version.
Workflow
1. Assess Current Situation
Get current problematic version:
# {{TICKET_PREFIX}}-445: Updated container name per Terminology Contract
ssh -i {{SSH_KEY_PATH}} {{REMOTE_USER}}@{{REMOTE_HOST}} "docker inspect {{PROJECT}}-dev-app | grep 'org.opencontainers.image.revision' | cut -d'\"' -f4"
Check current status:
curl -s http://{{REMOTE_HOST}}:3000/api/health 2>/dev/null || echo "Health check failed"
Document the issue for Linear ticket creation later.
2. List Available Rollback Targets
Show recent images on {{DEV_MACHINE}}:
ssh -i {{SSH_KEY_PATH}} {{REMOTE_USER}}@{{REMOTE_HOST}} "docker images {{REGISTRY}}/{{PROJECT_NAME}}/dev --format 'table {{.Tag}}\t{{.ID}}\t{{.CreatedAt}}'"
Cross-reference with git commits to show messages:
git log origin/dev -10 --oneline
3. Select Rollback Target
If argument provided (commit SHA like e9722d4):
- Use specified commit as rollback target
- Verify image exists with that SHA tag
If no argument provided:
- Display last 5 available images with commit messages
- Recommend previous stable version (before current)
- Ask user to confirm selection
Default behavior: Select image before current (most common rollback scenario)
4. Pull Rollback Image
Pull the specific version from registry:
ssh -i {{SSH_KEY_PATH}} {{REMOTE_USER}}@{{REMOTE_HOST}} "docker pull {{REGISTRY}}/{{PROJECT_NAME}}/dev:dev-{target-sha}"
If image not in registry (old version pruned), use local cached image.
5. Update Configuration
Create backup of current config:
ssh -i {{SSH_KEY_PATH}} {{REMOTE_USER}}@{{REMOTE_HOST}} "cd {{PROJECT_PATH}} && cp docker-compose.dev.yml docker-compose.dev.yml.backup.$(date +%Y%m%d_%H%M%S)"
Update docker-compose.dev.yml to use specific image tag:
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.
- 1mo ago First seen · 273 lines · 11 tokens per session scan C 9559e619d08e
rollback-dev is a command published in the GitHub repository bybren-llc/safe-agentic-workflow (423 stars, last pushed 2mo ago), licensed MIT. It adds 11 tokens to every session and 2,057 once invoked, about $0.0000 per session on Opus 5.5. A static security scan graded it C with 2 findings (reaches for credential files, makes network calls). It is 86% identical to remote-rollback, differing in 122 lines, and is treated as a copy.
Other commands, from other repositories
deployment
Basic production deployment setup for FastAPI applications.
dare-docker-compose
Este comando analisa a arquitetura definida no BLUEPRINT.md e gera um docker-compose.yml completo com todos os serviços necessários (App, DB, Cache, etc).
dare-dockerfile
Este comando analisa a stack do projeto (definida no DESIGN.md ou .cursorrules) e gera um Dockerfile otimizado para produção e desenvolvimento.
dare-docker
Containerização DARE com Dockerfile e docker-compose seguros, performantes e idiomáticos. Multi-stage, usuário não-root, healthchecks, redes isoladas.
secure-flow-harden-dockerfile-fips
Transform your Docker images to FIPS compliant by removing root users and ensuring security best practices. Make all production docker images in this repository FIPS compliant by hardening Dockerfiles and ensuring they do not run as root users.
clarify
Reduce spec ambiguity via targeted questions with adaptive auto-invocation (planning is 80% of success).