debug

A read-only debugging command that investigates a software problem by examining logs, application state, and git history.

In plain words
What is it for?
Use it to review recent changes, find relevant errors and warnings, inspect context files, and narrow down the cause of an issue.
Why use it?
It helps identify what went wrong without changing files, especially when a manual test or implementation produces an unexpected result.

Command

Install

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.

agentmods
npx agentmods add commands/adrielp/ai-engineering-harness/debug
Clone the repo
git clone --depth 1 https://github.com/adrielp/ai-engineering-harness
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 522 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.00522
Opus 5 $0.00000 $0.00261
Sonnet 5 $0.00000 $0.00104
Haiku 4.5 $0.00000 $0.00052

Measured 2d ago against content hash b28f1c30adbf, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

debug 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.

opencode/commands/debug.md · 110 lines

How it starts

The opening of the file, as written. The whole thing — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Debug

You are tasked with helping debug issues during manual testing or implementation. This command allows you to investigate problems by examining logs, state, and git history without editing files.

Initial Response

When invoked WITH a context file:

I'll help debug issues with [file name]. Let me understand the current state.

What specific problem are you encountering?
- What were you trying to test/implement?
- What went wrong?
- Any error messages?

I'll investigate the logs, state, and git history to help figure out what's happening.

When invoked WITHOUT parameters:

I'll help debug your current issue.

Please describe what's going wrong:
- What are you working on?
- What specific problem occurred?
- When did it last work?

I can investigate logs, state, and recent changes to help identify the issue.

Process Steps

Step 1: Understand the Problem

  1. Read any provided context (plan or ticket file)
  2. Quick state check:
    • Current git branch and recent commits
    • Any uncommitted changes

Step 2: Investigate the Issue

Spawn parallel Task agents:

Task 1 - Check Recent Logs:
Find and analyze logs for errors
Return: Key errors/warnings with timestamps
Task 2 - Application State:
Check the current application state
Return: Relevant state findings
Task 3 - Git and File State:
Understand what changed recently
Return: Git state and any file issues

Step 3: Present Findings

## Debug Report

### What's Wrong
[Clear statement of the issue]

### Evidence Found

**From Logs**:
- [Error/warning with timestamp]

**From Application State**:
- [Finding from state]

**From Git/Files**:
- [Recent changes that might be related]

### Root Cause
[Most likely explanation]

### Next Steps

1. **Try This First**:
   ```bash
   [Specific command or action]
  1. If That Doesn't Work:
    • [Alternative approach]

Can't Access?

Some issues might be outside my reach:

  • Browser console errors
  • External service state
  • System-level issues

Would you like me to investigate something specific further?

Read the full file on GitHub · 110 lines

Changes

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.

  1. 2d ago First seen · 110 lines · 0 tokens per session scan A b28f1c30adbf

Subscribe to this mod's changes

debug is a command published in the GitHub repository adrielp/ai-engineering-harness (20 stars, last pushed 2mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 522 tokens. 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.