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/rollbackgit 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/rollback)<a href="https://agentmods.dev/commands/dimitrigeelen/agentic-engineering-framework/rollback"><img src="https://agentmods.dev/badge/commands/dimitrigeelen/agentic-engineering-framework/rollback.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.00818 |
| Opus 5 | $0.00000 | $0.00409 |
| Sonnet 5 | $0.00000 | $0.00164 |
| Haiku 4.5 | $0.00000 | $0.00082 |
Grade A, and why
rollback 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:5050/health How it starts
The opening of the file, as written. The whole thing — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/rollback - Revert Production to Previous Version
Recovery skill for failed or problematic deployments. Reads deployment history, confirms with user, executes rollback, verifies health.
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: Read Deployment History
ls -t .context/deployments/*.yaml 2>/dev/null | head -5
If no deployment records exist, STOP and say: "No deployment records found in .context/deployments/. Nothing to roll back."
Read the most recent deployment record:
cat .context/deployments/$(ls -t .context/deployments/*.yaml | head -1 | xargs basename)
Present the deployment info:
## Last Deployment
- Timestamp: {timestamp}
- App: {app}
- Task: {task}
- Commit: {commit}
- Result: {result}
Step 3: Check Current Service State
export DOCKER_HOST=tcp://192.168.10.201:2375
docker service ls --filter name=watchtower
docker service ps watchtower_app --format '{{.ID}} {{.Image}} {{.CurrentState}}' | head -5
Present the current state: running image version, replica count, health.
Step 4: Confirm with User
This is a Tier 0 action. Present options and WAIT for explicit user confirmation:
## Rollback Options
1. Rollback watchtower_app to previous version (docker service rollback)
2. Cancel — do not rollback
Do NOT proceed without the user selecting option 1. If user selects 2 or anything else, abort.
Step 5: Execute Rollback
Only after user confirms option 1:
export DOCKER_HOST=tcp://192.168.10.201:2375
docker service rollback watchtower_app
Wait for convergence (up to 60 seconds):
for i in $(seq 1 30); do
RUNNING=$(docker service ps watchtower_app --filter desired-state=running --format '{{.CurrentState}}' | grep -c 'Running')
if [ "$RUNNING" -ge 2 ]; then
echo "Rollback converged: $RUNNING replicas running"
break
fi
sleep 2
done
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 · 122 lines · 0 tokens per session scan A 1f89bdbdf265
rollback 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 818 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.
schedules
Quick overview of all schedules across the platform.
status
Report on recent research activity and findings count.