agentmods.dev

plugins: Agent for Claude Code

.cursor/agents/dashboard-log-debugger.md

dashboard-log-debugger is an agent for Claude Code, Cursor from NotePlan/plugins. It costs 73 tokens per session (892 once invoked), scanned A, original, MIT.

A debugging agent for the jgclark.Dashboard NotePlan plugin. It traces dashboard startup, perspective changes, section refreshes, Apple Reminders data, and related plugin events through NotePlan’s structured log.

In plain words
What is it for?
Use it to investigate dashboard startup or refresh problems, perspective switching, Apple Reminders or REM issues, repeated data updates, plugin data calls, and JavaScript blocking.
Why use it?
It helps locate failures in asynchronous refresh paths and distinguishes which function ran and what data updates it sent. This makes it easier to form a focused hypothesis and apply a minimal fix.

Agent for Claude CodeCursor

Written for Cursor and Claude Code: installed under .cursor/, but also a Claude Code subagent (agents/*.md).

This is NotePlan/plugins's own configuration. It tells Claude Code and Cursor how to work on plugins itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything plugins configures →

not rated 204repo +1 changed 1mo ago A scan 73 tokens original MIT
View source ↗ NotePlan/plugins
Reuse

Borrowing it

Nothing to install: this file belongs to NotePlan/plugins. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/NotePlan/plugins/main/.cursor/agents/dashboard-log-debugger.md
Clone the repo
git clone --depth 1 https://github.com/NotePlan/plugins

Made for: Claude Code, Cursor.

Wrote 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.

agentmods badge for dashboard-log-debugger

README.md
[![agentmods](https://agentmods.dev/badge/agents/noteplan/plugins/dashboard-log-debugger/github.svg)](https://agentmods.dev/agents/noteplan/plugins/dashboard-log-debugger)
Your own site
<a href="https://agentmods.dev/agents/noteplan/plugins/dashboard-log-debugger"><img src="https://agentmods.dev/badge/agents/noteplan/plugins/dashboard-log-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.

agentmods 80×15 button for dashboard-log-debugger

Your own site · 80×15
<a href="https://agentmods.dev/agents/noteplan/plugins/dashboard-log-debugger"><img src="https://agentmods.dev/badge/agents/noteplan/plugins/dashboard-log-debugger.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 73 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 892 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00073 $0.00892
Opus 5.5 $0.00029 $0.00357
Sonnet 5.5 $0.00015 $0.00178
Haiku 4.5 $0.00007 $0.00089

Measured 1mo ago against content hash 03fe24f17887, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

dashboard-log-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.

.cursor/agents/dashboard-log-debugger.md · 48 lines

How it starts

The opening of the file, as written. The whole thing — 48 lines — stays where its author put it; the contents beside it link to each section on GitHub.

You are a Dashboard debugger for the NotePlan plugin jgclark.Dashboard.

When invoked:

  1. Read the latest relevant plugin log with the nplog skill (agents/skills/nplog/SKILL.md) -- never grep the raw log.
  2. Identify the run (showDashboardReact, reactWindowInitialisedSoStartGeneratingData, PERSPECTIVE_CHANGED, TB timer, etc.).
  3. Trace which refresh function ran and how many setPluginData / UPDATE_DATA payloads it sent.
  4. Form a hypothesis, make a minimal fix, add or update tests, and note CHANGELOG under the current first H2.

Logs

Use node scripts/nplog/nplog --json from the repo root. Full procedure: agents/skills/nplog/SKILL.md.

  • --last-run is the most recent Executing function, which is often a TB timer refreshSomeSections, not the startup you care about. Prefer --since 10m or --mode for showDashboardReact / reactWindowInitialisedSoStartGeneratingData.
  • --follow --wait-idle 5 after an x-callback. Do not read immediately; the log flushes in batches (can lag 20s+).
  • Exit code 1 means at least one emitted ERROR. Check that first.
  • Do not use the MCP per-plugin _MCP-console.log as evidence of a past run.

Refresh paths

  • refreshSomeSections: merge; one setPluginData; keep other rows. Default for 1-few codes.
  • incrementallyRefreshSomeSections: N merges; progressive pop-in. First launch and full Refresh.
  • batchReplaceSections: one wholesale replace. Perspective switch only.

Perspective switch already writes sections: [] before generation. Incremental merge-onto-empty would not leave leftover rows. Keep batch because: one cheap getGlobalSharedData while sections are empty, then a single write; the switch spinner hides pop-in so N round-trips buy nothing; skip header done-count recount.

setPluginData always getGlobalSharedDatas the whole WebView tree. A follow-up flag-only patch after a large send re-serializes the full section list back into the plugin and blocks paint. Fold spinner / firstRun / perspectiveChanging into the payload that already has the new sections.

Read the full file on GitHub · 48 lines

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. 1mo ago Changed 03fe24f17887
  2. 2mo ago First seen · 48 lines · 73 tokens per session scan A 18bc6895151e

Subscribe to this mod's changes

dashboard-log-debugger is an agent published in the GitHub repository NotePlan/plugins (204 stars, last pushed today), licensed MIT. It adds 73 tokens to every session and 892 once invoked, about $0.0003 per session on Opus 5.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-30.

Debugging
Related

Other agents, from other repositories

review-obsidian-guidelines

Reviews a diff of obsidian-reminder against Obsidian's community plugin guidelines and directory review rules that ESLint does not already enforce — manifest metadata, command naming, settings UI, styling, mobile compatibility, vault access APIs. Used by the pr-review workflow; read-only.

uphy/obsidian-reminder · 63 tokens

debugger

Diagnoses and fixes failed modules using root-cause analysis, not guessing.

TT-Wang/forge · 17 tokens

debugger

Investigate errors systematically to find root cause before attempting fixes. Gathers evidence, analyzes patterns, and forms testable hypotheses.

bostonaholic/rpikit · 28 tokens

loom-advisor

Read-only advisory agent for debugging and repeated failures. Spawned instead of a blind retry when an implementer has failed twice on the same task, or a bug resists straightforward diagnosis. Returns a root-cause diagnosis plus one concrete next step.

cosmix/loom · 53 tokens

evolve-retrospective

Failure post-mortem agent for the Evolve Loop. Fires only on Auditor FAIL or WARN verdicts. Reads cycle artifacts and produces a structured retrospective + failure-lesson YAML files. READ-ONLY outside the lessons directory.

mickeyyaya/evolve-loop · 51 tokens

type-reconstructor

Dedicated struct/class reconstruction from IDA Pro decompiled binaries. Scans every function for memory access patterns, merges evidence across the module, resolves vtable and COM interface layouts, and generates compilable C++ header files with per-field confidence annotations. Use for full-module or single-class…

marcosd4h/DeepExtractRuntime · 63 tokens