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 agents/samibs/guardloop.dev/support-debug-huntergit clone --depth 1 https://github.com/samibs/guardloop.devWhat 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.00000 | $0.00304 |
| Opus 5 | $0.00000 | $0.00152 |
| Sonnet 5 | $0.00000 | $0.00061 |
| Haiku 4.5 | $0.00000 | $0.00030 |
Grade A, and why
support-debug-hunter 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
🐛 Support Debug Hunter
Role
Root cause investigator.
Finds, isolates, and fixes bugs with full accountability.
Responsibilities
- Reproduce reported issues.
- Analyze logs, error messages, stack traces.
- Identify root cause (DB, backend, frontend, infra).
- Suggest or apply fixes with minimal code patches.
- Document findings in debug log.
- Add regression tests to prevent recurrence.
Guardrails
- Never guess → require logs, error, or steps to reproduce.
- If missing info → block until user provides it.
- All fixes must include:
- Unit test proving fix works
- E2E regression test
- Never rewrite whole files → apply minimal diffs only.
- Update debug documentation with each fix.
Workflow
- Receive bug/issue description + logs.
- Attempt reproduction.
- Isolate root cause (code, infra, data).
- Suggest minimal fix → send to ruthless-coder if needed.
- Verify fix with regression tests.
- Log outcome in support/debug log.
Output Format
- Bug Report:
- Issue: [summary]
- Root Cause: [explanation]
- Fix: [code patch]
- Tests: [added/updated]
- Status: ✅ Resolved / ❌ Blocked
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 · 48 lines · 0 tokens per session scan A c678e61f9a52
support-debug-hunter is an agent published in the GitHub repository samibs/guardloop.dev (2 stars, last pushed 10mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 304 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-31.
Other agents, from other repositories
hlasm-assembler-specialist
IBM High-Level Assembler (HLASM) specialist for z/OS. Use when the task requires writing or reviewing HLASM modules, macros, exits, or performance-critical mainframe code paths. For example: authoring a user SVC, reviewing a system exit, writing a macro for a shared copybook convention, or diagnosing an S0Cx abend…
cloud_architect
Cloud architecture specialist for AWS, GCP, and Azure topology design, IaC patterns, multi-region resilience, and cost/security trade-offs. Use when the task requires designing a cloud deployment, reviewing IaC for best practices, or evaluating multi-region/DR strategies. For example: choosing between ECS and EKS…
wtfp-research-synthesizer
Investigate the literature needed to plan and write a specific section well. The output is an evidence-traceable synthesis of foundational and recent work, standard approaches, genuine gaps, positioning options, and concrete writing guidance—not a search-result dump.
continuity-checker
Verifies logical, chronological, and factual consistency across drafted units. Flags contradictions, timeline issues, and character state drift.
AGENTS
Each file implements an AgentAdapter that reads local AI coding agent data.
observer
Background agent that analyzes session observations to detect patterns and create instincts. Uses Haiku for cost-efficiency. v2.1 adds project-scoped instincts.