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/mischasigtermans/laravel-altitude/debuggit clone --depth 1 https://github.com/mischasigtermans/laravel-altitudeWrote 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/mischasigtermans/laravel-altitude/debug)<a href="https://agentmods.dev/commands/mischasigtermans/laravel-altitude/debug"><img src="https://agentmods.dev/badge/commands/mischasigtermans/laravel-altitude/debug.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.00007 | $0.00384 |
| Opus 5 | $0.00003 | $0.00192 |
| Sonnet 5 | $0.00001 | $0.00077 |
| Haiku 4.5 | $0.00001 | $0.00038 |
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 6d 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
Debug - Investigate Errors
Investigate errors using available diagnostic tools.
Usage
/debug [error context]
Issue Classification
Error Type?
├── HTTP → Telescope requests, route logs
├── Database → Telescope queries, slow log
├── Queue → failed_jobs, Telescope jobs
└── Auth → Telescope requests, session
Investigation
1. Gather Context
If Herd MCP available (Laravel Herd Pro):
mcp__herd__get-logs # Application logs
mcp__herd__get-dumps # Dump output
If Telescope MCP installed (lucianotonet/laravel-telescope-mcp):
mcp__laravel-telescope__requests # HTTP with exceptions
mcp__laravel-telescope__exceptions # Stack traces
mcp__laravel-telescope__queries # Slow/failed queries
mcp__laravel-telescope__jobs # Failed jobs
mcp__laravel-telescope__logs # Application logs
mcp__laravel-telescope__mail # Email issues
Fallback:
- Read
storage/logs/laravel.log - Search for error messages
- Check
failed_jobstable
2. Trace
- Follow stack trace to file:line
- Read surrounding code
- Check related files
3. Report
## Debug Report
**Error:** [Exception] - [message]
**Location:** [file:line]
### Root Cause
[What's failing]
### Fix
[Code change]
Examples
/debug
/debug "500 on checkout"
/debug "jobs stuck"
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.
- 6d ago First seen · 79 lines · 7 tokens per session scan A 73f08e34e390
debug is a command published in the GitHub repository mischasigtermans/laravel-altitude (122 stars, last pushed 5mo ago), licensed MIT. It adds 7 tokens to every session and 384 once invoked, about $0.0000 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
replay
Summarize one Agent Monitor session by id — header plus a concise transcript recap.
doctor
Quick connectivity + health probe of the Agent Monitor dashboard.
tail-events
Show the latest N ingested events with timestamp, eventtype, and toolname.
errors
List the most recent APIError events with their session and a summary.
health
One-line reliability verdict (OK / DEGRADED / FAILING) for Claude Code usage.
slo
Print a quick SLO snapshot — completion rate, tool success rate, and error rate.