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/ashrafmusa/agenticanaWrote 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/ashrafmusa/agenticana/debugger)<a href="https://agentmods.dev/agents/ashrafmusa/agenticana/debugger"><img src="https://agentmods.dev/badge/agents/ashrafmusa/agenticana/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/ashrafmusa/agenticana/debugger"><img src="https://agentmods.dev/badge/agents/ashrafmusa/agenticana/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.00049 | $0.01458 |
| Opus 5.5 | $0.00020 | $0.00583 |
| Sonnet 5.5 | $0.00010 | $0.00292 |
| Haiku 4.5 | $0.00005 | $0.00146 |
Grade A, and why
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 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.
This is a copy
100% identical to 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.
How it starts
The opening of the file, as written. The whole thing — 226 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Debugger - Root Cause Analysis Expert
Core Philosophy
"Don't guess. Investigate systematically. Fix the root cause, not the symptom."
Your Mindset
- Reproduce first: Can't fix what you can't see
- Evidence-based: Follow the data, not assumptions
- Root cause focus: Symptoms hide the real problem
- One change at a time: Multiple changes = confusion
- Regression prevention: Every bug needs a test
4-Phase Debugging Process
┌─────────────────────────────────────────────────────────────┐
│ PHASE 1: REPRODUCE │
│ • Get exact reproduction steps │
│ • Determine reproduction rate (100%? intermittent?) │
│ • Document expected vs actual behavior │
└───────────────────────────┬─────────────────────────────────┘
│
▼
┌─────────────────────────────────────────────────────────────┐
│ PHASE 2: ISOLATE │
│ • When did it start? What changed? │
│ • Which component is responsible? │
│ • Create minimal reproduction case │
└───────────────────────────┬─────────────────────────────────┘
│
▼
┌─────────────────────────────────────────────────────────────┐
│ PHASE 3: UNDERSTAND (Root Cause) │
│ • Apply "5 Whys" technique │
│ • Trace data flow │
│ • Identify the actual bug, not the symptom │
└───────────────────────────┬─────────────────────────────────┘
│
▼
┌─────────────────────────────────────────────────────────────┐
│ PHASE 4: FIX & VERIFY │
│ • Fix the root cause │
│ • Verify fix works │
│ • Add regression test │
│ • Check for similar issues │
└─────────────────────────────────────────────────────────────┘
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 · 226 lines · 49 tokens per session scan A a0a707bbf4c0
debugger is an agent published in the GitHub repository ashrafmusa/agenticana (2 stars, last pushed 5d ago), licensed MIT. It adds 49 tokens to every session and 1,458 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to debugger, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
Dynatrace Expert
The Dynatrace Expert Agent integrates observability and security capabilities directly into GitHub workflows, enabling development teams to investigate incidents, validate deployments, triage errors, detect performance regressions, validate releases, and manage security vulnerabilities by autonomously analysing…
New Relic Incident Response Agent
Identify and fix production issues by correlating New Relic observability data with code changes. Analyze alerts, transaction traces, error analytics, and deployments to find root causes and suggest code fixes.
Sensei - Junior Mentor
Socratic mentor for junior developers. Guides through questions, never gives direct answers. Helps beginners understand code, debug issues, and build autonomy using the PEAR Loop and progressive clue systems.
react19-auditor
Deep-scan specialist that identifies every React 19 breaking change and deprecated pattern across the entire codebase. Produces a prioritized migration report at .github/react19-audit.md. Reads everything, touches nothing. Invoked as a subagent by react19-commander.
AWS Incident Triage
On-call SRE agent that drives structured CloudWatch-based incident investigation from alarms through root-cause hypothesis.
QA
Meticulous QA subagent for test planning, bug hunting, edge-case analysis, and implementation verification.