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/deploy-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.00350 |
| Opus 5 | $0.00005 | $0.00175 |
| Sonnet 5 | $0.00002 | $0.00070 |
| Haiku 4.5 | $0.00001 | $0.00035 |
Grade A, and why
deploy-dev 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.
What it actually says
📋 TEMPLATE: This command is a template. See "Customization Guide" below to adapt for your infrastructure.
DEPRECATED: This command is an alias to
/remote-deploy. Use/remote-deploydirectly.
This command calls /remote-deploy which is the canonical command for deploying to {{DEV_MACHINE}}.
Usage
/remote-deploy
Why Deprecated?
Per {{TICKET_PREFIX}}-445, we canonicalized around /remote-* and /local-* naming:
/remote-*= {{DEV_MACHINE}} operations (staging-first, then dev)/local-*= Local machine operations
Related Commands
/remote-deploy- Canonical - Deploy latest image to {{DEV_MACHINE}}/remote-status- Check if {{DEV_MACHINE}} needs update/remote-health- Health dashboard for {{DEV_MACHINE}}/remote-logs- View {{DEV_MACHINE}} container logs/remote-rollback- Rollback {{DEV_MACHINE}} to previous image
Customization Guide
To adapt this command for your infrastructure, replace these placeholders:
| Placeholder | Description | Example |
|---|---|---|
{{TICKET_PREFIX}} |
Your Linear ticket prefix | WOR, PROJ, TASK |
{{DEV_MACHINE}} |
Your remote dev machine name | Pop OS, staging, dev-server |
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 · 41 lines · 11 tokens per session scan A c9141805cd43
deploy-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 350 once invoked, about $0.0001 per session on Opus 5. 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-08-30.
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.