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/bybren-llc/safe-agentic-workflow/rollback-devgit clone --depth 1 https://github.com/bybren-llc/safe-agentic-workflowWhat 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.00011 | $0.02057 |
| Opus 5 | $0.00005 | $0.01028 |
| Sonnet 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 2d 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.
- 2d 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 (404 stars, last pushed 1mo ago), licensed MIT. It adds 11 tokens to every session and 2,057 once invoked, about $0.0001 per session on Opus 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
concentrate-forces
用集中兵力方法在多个任务中锁定主攻目标。.
spark-prairie-fire
用星火燎原方法为从零起步的任务选择根据地和最小切入口。.
review
Review the current diff for violations of the conventions in AGENTS.md and .cursor/rules/. Report findings ordered by severity; do not fix anything unless asked.
plan-status
Render the current plan tree. Alias for /aura-frog:plan status (v3.7.2+).
help
Category: System Syntax: /help [command|topic].
adv-gemini-research
Deep research query via Gemini with Google Search grounding.