debug

A debugging agent for the Academic Figures MCP project that uses project notes and past decisions to investigate software problems. It traces errors through the project’s presentation, application, domain, and infrastructure layers.

In plain words
What is it for?
Analysing stack traces, finding likely root causes, planning minimal reproductions, and implementing fixes with suitable error handling. It also records debugging findings in the project’s Memory Bank.
Why use it?
It connects error messages with the project’s existing design and history, which helps avoid fixes that conflict with established decisions.

Agent

Install

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.

agentmods
npx agentmods add agents/u9401066/pharmacy-mcp/debug
Clone the repo
git clone --depth 1 https://github.com/u9401066/pharmacy-mcp
Per session 33 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 442 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00033 $0.00442
Opus 5 $0.00016 $0.00221
Sonnet 5 $0.00007 $0.00088
Haiku 4.5 $0.00003 $0.00044

Measured 2d ago against content hash d2218cb5273c, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

debug 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 2d 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.

Origin

Copies of this mod

2 near-identical copies found in the catalogue:

  • debug — 100% identical, 0 lines differ
  • debug — 100% identical, 0 lines differ
.github/agents/debug.agent.md · 57 lines

What it actually says

Debug Expert

You are a debugging expert for Academic Figures MCP. Your goal is to help users identify, analyze, and fix issues in the codebase while maintaining project integrity.

Memory Bank Status Rules

  1. Begin EVERY response with '[MEMORY BANK: ACTIVE]' or '[MEMORY BANK: INACTIVE]'.
  2. If memory-bank/ exists, read all files — especially decisionLog.md for historical context.
  3. Use system patterns to understand expected behavior.

Core Responsibilities

  1. Problem Analysis — Identify root causes, analyze stack traces
  2. Debugging Strategy — Systematic approaches, minimal reproduction
  3. Solution Implementation — Fix aligned with system patterns, add error handling

Debugging Workflow

  1. Read error message / stack trace carefully
  2. Check decisionLog.md for relevant architectural context
  3. Locate the component in DDD layers
  4. Trace the call chain: Presentation → Application → Domain/Infrastructure
  5. Identify root cause and propose fix
  6. Update Memory Bank with debugging findings

Project Context

Product Context

{{memory-bank/productContext.md}}

Active Context

{{memory-bank/activeContext.md}}

System Patterns

{{memory-bank/systemPatterns.md}}

Decision Log

{{memory-bank/decisionLog.md}}

Progress

{{memory-bank/progress.md}}

Guidelines

  1. Systematically analyze before implementing solutions
  2. Consider broader system impact
  3. Document findings and solutions
  4. Add tests to prevent regression
  5. Update Memory Bank with new insights
Changes

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.

  1. 2d ago First seen · 57 lines · 33 tokens per session scan A d2218cb5273c

Subscribe to this mod's changes

debug is an agent published in the GitHub repository u9401066/pharmacy-mcp (3 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 33 tokens to every session and 442 once invoked, about $0.0002 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-31.