Getting it into your agent
There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.
Wrote 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/skills/sliamh11/deus/debug)<a href="https://agentmods.dev/skills/sliamh11/deus/debug"><img src="https://agentmods.dev/badge/skills/sliamh11/deus/debug/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/sliamh11/deus/debug"><img src="https://agentmods.dev/badge/skills/sliamh11/deus/debug.svg" alt="Reviewed on agentmods" width="80" 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.00040 | $0.02901 |
| Opus 5.5 | $0.00016 | $0.01160 |
| Sonnet 5.5 | $0.00008 | $0.00580 |
| Haiku 4.5 | $0.00004 | $0.00290 |
Grade D, and why
debug scanned grade D 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 1mo 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.
--dangerously-skip-permissions cannot be used with root/sudo privileges Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
rm -rf data/sessions/ This is a copy
94% identical to debug — 32 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.
How it starts
The opening of the file, as written. The whole thing — 350 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Deus Container Debugging
This guide covers debugging the containerized agent execution system.
Architecture Overview
Host (macOS) Container (Linux VM)
─────────────────────────────────────────────────────────────
src/container-runner.ts container/agent-runner/
│ │
│ spawns container │ runs Claude Agent SDK
│ with volume mounts │ with MCP servers
│ │
├── data/env/env ──────────────> /workspace/env-dir/env
├── groups/{folder} ───────────> /workspace/group
├── data/ipc/{folder} ────────> /workspace/ipc
├── data/sessions/{folder}/.claude/ ──> /home/node/.claude/ (isolated per-group)
└── (main only) project root ──> /workspace/project
Important: The container runs as user node with HOME=/home/node. Session files must be mounted to /home/node/.claude/ (not /root/.claude/) for session resumption to work.
Log Locations
| Log | Location | Content |
|---|---|---|
| Main app logs | logs/deus.log |
Host-side WhatsApp, routing, container spawning |
| Main app errors | logs/deus.error.log |
Host-side errors |
| Container run logs | groups/{folder}/logs/container-*.log |
Per-run: input, mounts, stderr, stdout |
| Claude sessions | ~/.claude/projects/ |
Claude Code session history |
Enabling Debug Logging
Set LOG_LEVEL=debug for verbose output:
# For development
LOG_LEVEL=debug npm run dev
# For launchd service (macOS), add to plist EnvironmentVariables:
<key>LOG_LEVEL</key>
<string>debug</string>
# For systemd service (Linux), add to unit [Service] section:
# Environment=LOG_LEVEL=debug
Debug level shows:
- Full mount configurations
- Container command arguments
- Real-time container stderr
Common Issues
1. "Claude Code process exited with code 1"
Check the container log file in groups/{folder}/logs/container-*.log
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.
- 1mo ago First seen · 350 lines · 40 tokens per session scan D 242464666b99
debug is a skill published in the GitHub repository sliamh11/Deus (52 stars, last pushed today), licensed MIT. It adds 40 tokens to every session and 2,901 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it D with 2 findings (asks for root, recursive force delete). It is 94% identical to debug, differing in 32 lines, and is treated as a copy.
Other skills, from other repositories
roadmap-build
Build or repair a roadmap that agents can actually execute, not just read. Produces a single validated YAML source of truth, generated views, definitions of done with evidence kinds, a task pool linked on two axes, an idea intake queue, and three standing checks that keep it honest. Use when asked to "build a…
github-triage
Nightly GitHub triage for the owner's product repositories, run by Miles on the nightshift host. Answers "what requires attention now, what blocks the team or a release, which open PRs are ready or problematic, what first?", writes a decision-oriented report plus a decision-board data file into the owner's private…
telegram-output-formatting
How to format Telegram output for the owner — short summaries with emoji titles, bullet-point lists, and full reports committed to plur-space. Applies to every report, briefing, task summary, and intelligence output delivered in Telegram DMs.
memcord
Privacy-first, self-hosted chat memory for OpenClaw — save and recall conversation history across sessions without any cloud dependency.
decision-board
Present decisions to the owner as a decision board: a local, PLUR-branded HTML page with one decision per row, a suggested answer on each, a note field, and a Save that hands the choices back to Claude as a JSON file. This skill fixes how the page looks and behaves. The session supplies the content, and the owner…
Research for Datacore
Automated research — source processing, podcast generation, and knowledge extraction.