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/archubbuck/workspace-architectWrote 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/agents/archubbuck/workspace-architect/gem-debugger)<a href="https://agentmods.dev/agents/archubbuck/workspace-architect/gem-debugger"><img src="https://agentmods.dev/badge/agents/archubbuck/workspace-architect/gem-debugger/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/agents/archubbuck/workspace-architect/gem-debugger"><img src="https://agentmods.dev/badge/agents/archubbuck/workspace-architect/gem-debugger.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.00021 | $0.00704 |
| Opus 5.5 | $0.00008 | $0.00282 |
| Sonnet 5.5 | $0.00004 | $0.00141 |
| Haiku 4.5 | $0.00002 | $0.00070 |
Grade A, and why
gem-debugger 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 9d 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.
This is a copy
100% identical to gem-debugger — 0 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.
What it actually says
DEBUGGER
Root-cause analysis, stack trace diagnosis, regression bisection, error reproduction.
<output_format>
{
"status": "completed | failed | needs_revision",
"reason": "string",
"fail": "fixable | needs_replan | escalate | flaky | regression | new_failure | platform_specific",
"handoff": {
"debugger_diagnosis": {
"root_cause": "string",
"target_files": ["string"],
"reproduction": { "steps": ["string"], "expected": "string", "actual": "string" },
"fix_recommendations": ["string"]
},
"lint_rule_recommendations": [{ "name": "string", "type": "built-in | custom", "files": ["string"] }]
},
"learn": "string"
}
</output_format>
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.
- 9d ago Changed · -2 lines ad8c0590a28d
- 1mo ago Changed · -52 lines 4a0740eea3c0
- 1mo ago Changed · +4 lines e98aeb02ca4d
- 1mo ago First seen · 112 lines · 21 tokens per session scan A 3beac33373fc
gem-debugger is an agent published in the GitHub repository archubbuck/workspace-architect (19 stars, last pushed yesterday), licensed ISC. It adds 21 tokens to every session and 704 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to gem-debugger, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
AL Debugging Specialist
AL Debugging specialist for Business Central. Expert in troubleshooting, root cause analysis, and resolving AL development issues using debugging tools and techniques.
systematic-debugging
Structured 4-phase debugging agent — problem assessment, root cause investigation, targeted fix, quality assurance with regression tests.
agentmaster-retro
Transcript-driven analyze-fix-verify loop for the agentmaster skill suite itself. Use after a pipeline run leaves artifacts behind — .transcripts/ snapshots, root-level run transcripts, generated docs, or accumulated telemetry — when the user wants the suite's own skills to keep improving from real usage. Grades…
code-analyst
Mid-cost interpretation — trace how code works across files, reproduce and analyze test failures, research dependency changelogs and upgrade impact, run code-graph and architecture queries. Use when the answer requires reading between files, interpreting command output, or external research. Also the escalation target…
debug
../../src/claude/agents/debug.md.
debug
Debug your application to find and fix a bug.