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/enuno/dokploy/dokploy-troubleshootgit clone --depth 1 https://github.com/enuno/dokployWrote 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/enuno/dokploy/dokploy-troubleshoot)<a href="https://agentmods.dev/commands/enuno/dokploy/dokploy-troubleshoot"><img src="https://agentmods.dev/badge/commands/enuno/dokploy/dokploy-troubleshoot.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.00013 | $0.07099 |
| Opus 5 | $0.00006 | $0.03549 |
| Sonnet 5 | $0.00003 | $0.01420 |
| Haiku 4.5 | $0.00001 | $0.00710 |
Grade C, and why
dokploy-troubleshoot scanned grade C 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.
Reaches for credential fileshighPrivilege escalation
SSH keys, cloud credentials, git-credentials, .npmrc, /etc/shadow: reading these is how a config file becomes a credential leak.
/dokploy-troubleshoot nextcloud --host dokploy.example.com --user dokployuser --key ~/.ssh/id_rsa Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
test: ["CMD", "curl", "-f", "http://localhost:3000/api/health"] How it starts
The opening of the file, as written. The whole thing — 1,141 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Troubleshoot Deployed Dokploy Application
Diagnose and fix issues with applications deployed using Dokploy templates from this repository. Uses MCP server as primary diagnostic tool, with SSH for deeper system-level debugging when needed.
Invocation
/dokploy-troubleshoot <app-name>
/dokploy-troubleshoot <app-name> --host <hostname> --user <username> --key <path>
Examples:
# Troubleshoot using MCP server only (default)
/dokploy-troubleshoot grafana
# Troubleshoot with SSH diagnostics available
/dokploy-troubleshoot nextcloud --host dokploy.example.com --user dokployuser --key ~/.ssh/id_rsa
# Custom SSH configuration
/dokploy-troubleshoot pocketbase --host 192.168.1.100 --user root --key ~/.ssh/homelab_key
Diagnostic Hierarchy
┌─────────────────────────────────────────────┐
│ Phase 1: MCP Server Diagnostics (Primary) │
│ • Application status and health │
│ • Configuration validation │
│ • Deployment logs and events │
│ • Domain/routing checks │
│ • Make configuration changes │
│ • Monitor redeployments │
└───────────────────┬─────────────────────────┘
│
├─[Issue Resolved?]──Yes──► Done
│
No
│
▼
┌─────────────────────────────────────────────┐
│ Phase 2: SSH Deep Diagnostics (Secondary) │
│ • Container-level debugging │
│ • System resource analysis │
│ • Network connectivity tests │
│ • File system and volume inspection │
│ • Manual Docker commands │
└─────────────────────────────────────────────┘
Key Principle: MCP first, SSH second. Only escalate to SSH when MCP diagnostics are insufficient.
Workflow
Step 1: Parse Arguments
Extract application name and optional SSH connection parameters:
Required:
app-name: Name of the deployed application (matches blueprint name)
Optional SSH flags:
--host <hostname>: Remote Dokploy server hostname or IP
--user <username>: SSH username (default: inferred from MCP server config)
--key <path>: Path to SSH private key (default: ~/.ssh/id_rsa)
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 · 1,141 lines · 13 tokens per session scan C 30d3faf22ecf
dokploy-troubleshoot is a command published in the GitHub repository enuno/dokploy (2 stars, last pushed 23d ago), licensed Apache-2.0. It adds 13 tokens to every session and 7,099 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it C with 2 findings (reaches for credential files, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
meta-errors
Analyze error patterns and prevention recommendations.
dumpstack
Helps examine thread call stacks. While clrstack is more commonly used for managed call stacks, dumpstack can also be used to inspect stack frames, including native ones.
printexception
Prints information about an exception object.
name2ee
Displays the MethodTable and MethodDesc structures for a specified method or type name.
clrmodules
Lists the managed modules in the process.
dumpmt
Displays details about method tables (MethodTable).