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/armanzeroeight/fastagent-plugins/debug-tracegit clone --depth 1 https://github.com/armanzeroeight/fastagent-pluginsWhat 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.00010 | $0.00255 |
| Opus 5 | $0.00005 | $0.00128 |
| Sonnet 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 yesterday.
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.
- yesterday 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 1mo ago), licensed MIT. It adds 10 tokens to every session and 255 once invoked, about $0.0001 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
MIGRATE_DESIGN
Design doc for the migration tool PR. Author: Sol ([email protected]). Co-authored-by: wakesync.
tech-debt
Run bun run check:fix and then bunx knip and identify unused files and functions to refactor the project and simplify. Look at the deprecated features and confirm with the user to delete them. Look at the dependencies and remove the ones that are not needed based on knip results.
commit
Act as a senior software engineer to commit changes to the repository in non-interactive modes ONLY, using the following template.
aidd-churn
Rank files by hotspot score to identify prime candidates for refactoring before PR review.
doctor
Diagnose installation health. Check Node, CDP bridge, rn-fast-runner (iOS), rn-android-runner (Android), maestro-runner, simulators, Metro, CDP, injected helpers, ffmpeg, physical devices, plugin version, Vercel rules sync. Reports what's missing — does NOT modify your project.
workflow-router
Route to the appropriate spec-driven workflow command based on the user's intent.