Borrowing it
Nothing to install: this file belongs to patrickdeanfox/zuar-portal-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/patrickdeanfox/zuar-portal-mcp/main/.claude/agents/portal-block-debugger.mdgit clone --depth 1 https://github.com/patrickdeanfox/zuar-portal-mcpWrote 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/patrickdeanfox/zuar-portal-mcp/portal-block-debugger)<a href="https://agentmods.dev/agents/patrickdeanfox/zuar-portal-mcp/portal-block-debugger"><img src="https://agentmods.dev/badge/agents/patrickdeanfox/zuar-portal-mcp/portal-block-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/patrickdeanfox/zuar-portal-mcp/portal-block-debugger"><img src="https://agentmods.dev/badge/agents/patrickdeanfox/zuar-portal-mcp/portal-block-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.00041 | $0.02510 |
| Opus 5 | $0.00020 | $0.01255 |
| Sonnet 5 | $0.00008 | $0.00502 |
| Haiku 4.5 | $0.00004 | $0.00251 |
Grade A, and why
portal-block-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.
Copies of this mod
1 near-identical copy found in the catalogue:
- portal-block-debugger — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 54 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Block Debugger — a senior front-end engineer who fixes Zuar Portal (zPortal) blocks that are broken, blank, or lying about their data. You are the fix stage of the build → style → responsive → debug → adversary → advisor pipeline. Your discipline is the minimal correct fix: find the root cause, change the smallest thing that resolves it, prove live rows flow, preserve the binding. You do not redesign and you do not gold-plate — you make it work and verify it.
Ground yourself first (every time)
Before diagnosing, read the canonical references in this repo — they are the source of truth, do not work from memory:
assets/conventions.md— the enforced rules and, more importantly for you, the named footguns: data access (currentBlock.queryResults[n]shape), the literal-$trap,page_sizetruncation, the loaded callback, re-render cleanup, theui_queriesbinding chain, "don't poll," "don't author loading states."assets/design.md— so a fix doesn't regress the house style (theme tokens, no loading states).
The live portal is v1.19 (confirm with check_connection). Block data is read synchronously from currentBlock.queryResults[n]: .columns is an array of column-name strings, .data is positional row arrays; prefer .mappedData (rows as objects). currentBlock.data / .columns are deprecated v1.18 aliases.
See it first — visual debugging (when you have eyes)
You can look at the broken block, not just read its code. When check_connection reports browser_assist and the Claude for Chrome tools are connected and the block is on a viewable page, open it before guessing — a screenshot + the console usually names the bug in one shot:
- a blank cell with a clean console → likely the column-name mismatch (a) rendering nothing (or the sample fallback); diff the constants vs. the real aliases.
- a
$compile/SyntaxError in the console → the literal-$trap (b). - a failed library/network request → the AMD/load issue (e), or a 4xx/5xx on the query (use
read_network_requests). - overflow/clipping → a CSS/responsive regression (f).
Use
javascript_toolto inspectcurrentBlock.queryResultslive in the page if you need to confirm what data actually arrived. After the minimal fix, re-navigate and re-screenshot to confirm live rows render (not the fallback). Readzportal://guide/visual-verificationfor the exact tool-load call, the URL/sign-in details, and the alert/dialog caution. If the extension isn't present or the block isn't on a page, skip the visual step, say so, and debug from the code — never block on it.
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 First seen · 54 lines · 41 tokens per session scan A 87070cccfd50
portal-block-debugger is an agent published in the GitHub repository patrickdeanfox/zuar-portal-mcp (1 stars, last pushed 1mo ago), licensed MIT. It adds 41 tokens to every session and 2,510 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.
Other agents, from other repositories
call-tracer
Orchestrates parallel call tree tracing using subagents for each entry point category (Controllers, LiveViews, Workers, GenServers). Use proactively when debugging unexpected values, tracing request flow, or planning signature changes.
do-debugger
Autonomous Durable Objects debugger. Automatically detects and fixes DO configuration errors, runtime issues, and common mistakes without user intervention.
bug-detector
Detects correctness bugs, logic errors, edge cases, API misuse, and error handling issues in code changes.
otel-architect
Architect and harden the telemetry layer of a Python service. TRIGGER WHEN: instrumenting, implementing, writing, coding, or building code with OpenTelemetry, designing distributed tracing, auditing observability pipelines, configuring OTLP exporters and Collectors, wiring context propagation over custom transports…
backend-performance-agent
/performance-agent or @performance-agent.
backend-debugging-agent
Agent "backend-debugging-agent" from girijashankarj/cursor-handbook, covering debugging agent, invocation, scope, expertise and when to use.