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/dev-healthgit 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/dev-health)<a href="https://agentmods.dev/commands/bybren-llc/safe-agentic-workflow/dev-health"><img src="https://agentmods.dev/badge/commands/bybren-llc/safe-agentic-workflow/dev-health.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.00009 | $0.00327 |
| Opus 5 | $0.00005 | $0.00163 |
| Sonnet 5 | $0.00002 | $0.00065 |
| Haiku 4.5 | $0.00001 | $0.00033 |
Grade A, and why
dev-health 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 7d 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.
This is a copy
88% identical to check-docker-status — 12 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.
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-health. Use/remote-healthdirectly.
This command calls /remote-health which is the canonical command for {{DEV_MACHINE}} health checks.
Usage
/remote-health
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-health- Canonical - Health dashboard for {{DEV_MACHINE}}/remote-status- Check if {{DEV_MACHINE}} needs update/remote-deploy- Deploy latest image to {{DEV_MACHINE}}/remote-logs- View {{DEV_MACHINE}} container logs
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.
- 7d ago First seen · 40 lines · 9 tokens per session scan A 59756806d98b
dev-health is a command published in the GitHub repository bybren-llc/safe-agentic-workflow (406 stars, last pushed 1mo ago), licensed MIT. It adds 9 tokens to every session and 327 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it A with 0 findings. It is 88% identical to check-docker-status, differing in 12 lines, and is treated as a copy.
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.