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/local-deploygit 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/local-deploy)<a href="https://agentmods.dev/commands/bybren-llc/safe-agentic-workflow/local-deploy"><img src="https://agentmods.dev/badge/commands/bybren-llc/safe-agentic-workflow/local-deploy.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.00008 | $0.02983 |
| Opus 5 | $0.00004 | $0.01491 |
| Sonnet 5 | $0.00002 | $0.00597 |
| Haiku 4.5 | $0.00001 | $0.00298 |
Grade B, and why
local-deploy scanned grade B 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 4d 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
sudo lsof -i :3000 Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s http://localhost:3000/api/health | jq How it starts
The opening of the file, as written. The whole thing — 471 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Deploy the latest Docker image from GitHub Container Registry to your LOCAL machine's Docker. Works on any machine with Docker Desktop or Docker Engine installed.
Usage
/local-deploy # Deploy using dev mode (source-mounted, hot-reload)
/local-deploy --staging # Deploy using staging mode (self-contained, production-like)
/local-deploy --rebuild # Trigger GitHub Actions build first, then deploy
/local-deploy --staging --rebuild # Build and deploy to staging mode
Deployment Modes
| Mode | Flag | Container | Use Case |
|---|---|---|---|
| Development (default) | (none) | {{PROJECT_NAME}}-dev-app |
Active development with hot-reload (STANDARD port 3000) |
| Staging | --staging |
{{PROJECT_NAME}}-staging-app |
Production-like, self-contained, survives git operations (port 3001) |
| Both | --both |
Both containers | Run dev and staging simultaneously ({{TICKET_PREFIX}}-400/{{TICKET_PREFIX}}-401) |
When to use each mode:
- Dev mode: You're actively writing code and want hot-reload (STANDARD port 3000)
- Staging mode: Testing, demos, or when you need stability during git operations (port 3001)
- Both modes: Run both simultaneously for testing migrations, feature comparison, etc.
Workflow
1. Parse Arguments
Check flags:
# Check command arguments
if [[ "$*" == *"--staging"* ]]; then
MODE="staging"
else
MODE="development"
fi
if [[ "$*" == *"--rebuild"* ]]; then
REBUILD=true
else
REBUILD=false
fi
2. Pre-Deployment Status Check
Get current running status (check both container types):
# Check for staging container
docker ps --filter name={{PROJECT_NAME}}-staging-app --format '{{.Names}}\t{{.Status}}'
# Check for dev container ({{TICKET_PREFIX}}-400: updated container name)
docker ps --filter name={{PROJECT_NAME}}-dev-app --format '{{.Names}}\t{{.Status}}'
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.
- 4d ago First seen · 471 lines · 8 tokens per session scan B ecce4c508329
local-deploy is a command published in the GitHub repository bybren-llc/safe-agentic-workflow (406 stars, last pushed 1mo ago), licensed MIT. It adds 8 tokens to every session and 2,983 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it B with 2 findings (asks for root, 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
help
Category: System Syntax: /help [command|topic].
translate-docs
翻译项目文档到指定语言.
review-tasks
审查任务的忠实度、可执行性、依赖关系与验证.
clarify
Reduce spec ambiguity via targeted questions with adaptive auto-invocation (planning is 80% of success).
tasks-to-issues
将现有任务转换为该功能的可操作 GitHub Issues.
ultrathink
Enter deep craftsman mode - question everything, plan like Da Vinci, craft insanely great solutions, then materialize to roadmap.