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.
git clone --depth 1 https://github.com/armanzeroeight/fastagent-pluginsWrote 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/armanzeroeight/fastagent-plugins/debug-trace)<a href="https://agentmods.dev/commands/armanzeroeight/fastagent-plugins/debug-trace"><img src="https://agentmods.dev/badge/commands/armanzeroeight/fastagent-plugins/debug-trace/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/commands/armanzeroeight/fastagent-plugins/debug-trace"><img src="https://agentmods.dev/badge/commands/armanzeroeight/fastagent-plugins/debug-trace.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.00010 | $0.00255 |
| Opus 5.5 | $0.00004 | $0.00102 |
| Sonnet 5.5 | $0.00002 | $0.00051 |
| Haiku 4.5 | $0.00001 | $0.00026 |
Grade A, and why
debug-trace 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 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.
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 Trace Analysis
Investigate the issue: $ARGUMENTS
Analysis Steps
-
Understand the Error:
- Parse error message and stack trace
- Identify failure point
- Note error type and context
-
Trace Execution Path:
- Follow code flow leading to error
- Identify relevant functions/methods
- Check variable states and conditions
-
Form Hypotheses:
- List possible root causes
- Prioritize by likelihood
- Consider recent changes: !
git log --oneline -10
-
Identify Root Cause:
- Explain what went wrong
- Explain why it happened
- Show evidence supporting diagnosis
-
Suggest Fix:
- Provide specific code changes
- Explain why fix works
- Suggest tests to prevent recurrence
Present findings clearly with:
- Root cause explanation
- Evidence (stack trace, code snippets)
- Recommended fix
- Prevention strategy
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 · 43 lines · 10 tokens per session scan A 3347b92c1e69
debug-trace is a command published in the GitHub repository armanzeroeight/fastagent-plugins (29 stars, last pushed 2mo ago), licensed MIT. It adds 10 tokens to every session and 255 once invoked, about $0.0000 per session on Opus 5.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
debug-screen
Diagnose why the current screen is broken, showing unexpected content, or crashing. Gathers parallel evidence from all layers and applies a targeted fix.
ci-readout
Generate a comprehensive summary of recent CI runs and failing jobs.
quality-gate
Run formatter, linter, and type checks for a file or directory. Report remediation steps.
create-repro
Isolate a bug report into a minimal, standalone reproduction script or test case.
cleanup
Run a systematic cleanup on the provided code to resolve smells, simplify complexity, and enforce best practices.
debt-audit
Perform a technical debt audit on the specified components and generate a prioritized remediation roadmap.