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/statusgit clone --depth 1 https://github.com/bybren-llc/safe-agentic-workflowWrote 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/status)<a href="https://agentmods.dev/commands/bybren-llc/safe-agentic-workflow/status"><img src="https://agentmods.dev/badge/commands/bybren-llc/safe-agentic-workflow/status.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.1 | $0.00000 | $0.00678 |
| Opus 5 | $0.00000 | $0.00339 |
| Sonnet 5 | $0.00000 | $0.00136 |
| Haiku 4.5 | $0.00000 | $0.00068 |
Grade A, and why
status scanned grade A with 0 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.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.
description = "Check if remote Docker environment needs updating"
prompt = """
Remote Status Command
Compare the Docker image running on your remote host with the latest image in the registry.
Deployment Modes
| Mode | Container Name | Port | Use Case |
|---|---|---|---|
| Development | {PROJECT}-dev |
3000 |
Hot-reload, source-mounted, local dev tools |
| Staging | {PROJECT}-staging |
3001 |
Production-like, self-contained, stable |
Workflow
1. Get Running Container Info
Check running container on remote host via SSH:
ssh -i {SSH_KEY_PATH} {REMOTE_USER}@{REMOTE_HOST} "docker ps --filter name={PROJECT} --format 'table {{.Names}}\t{{.Image}}\t{{.Status}}'"
Extract commit SHA from running container:
ssh -i {SSH_KEY_PATH} {REMOTE_USER}@{REMOTE_HOST} "docker inspect {CONTAINER_NAME} | grep 'org.opencontainers.image.revision'"
2. Get Latest Registry Image Info
Check latest commit on your main branch:
!{git fetch origin main && git log origin/main -1 --format='%H %s'}
Check latest GitHub Actions build status:
!{gh run list --workflow="Build and Push Docker Image" --limit 3 2>/dev/null || echo "Check CI manually"}
3. Compare and Report Status
If commit SHAs match:
- Remote host is up-to-date
- Report current version info
- Show uptime
- No action needed
If commit SHAs differ:
- Update available
- Show current vs latest commits
- Check if CI build is complete
- If build in progress: show estimated completion
- If build complete: provide deployment command
4. Output Format
Display comprehensive status:
Docker Image Status Check
Remote Environment (Running):
Container: {CONTAINER_NAME}
Status: Up 7 hours (healthy)
Commit: e9722d4 - previous commit message
Container Registry (Latest):
Commit: 3a49b85 - latest commit message
Build: Complete (31 seconds ago)
Status: Ready to deploy
Result: UPDATE AVAILABLE
To deploy update: /remote:deploy
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 · 109 lines · 0 tokens per session scan A 7cdc8ade055d
status is a command published in the GitHub repository bybren-llc/safe-agentic-workflow (406 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 678 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other commands, from other repositories
ci-setup
Setup continuous integration pipeline.
ops-k8s
Kubernetes deployment and orchestration.
validate-staging
Validate staging deployment before production through automated test review, rollback capability testing, guided manual validation, and optional gap capture for feedback loops.
deploy-check
Post-merge CD verification. Run after merging a PR to main.
arckit.devops
Create DevOps strategy with CI/CD pipelines, IaC, container orchestration, and developer experience.
sparc-devops
🚀 DevOps - You are the DevOps automation and infrastructure specialist responsible for deploying, managing, ...