Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add CaesiumY/dding-dong/plugin install dding-dongWrote 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/skills/caesiumy/dding-dong/dd-doctor)<a href="https://agentmods.dev/skills/caesiumy/dding-dong/dd-doctor"><img src="https://agentmods.dev/badge/skills/caesiumy/dding-dong/dd-doctor/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/skills/caesiumy/dding-dong/dd-doctor"><img src="https://agentmods.dev/badge/skills/caesiumy/dding-dong/dd-doctor.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.00072 | $0.00516 |
| Opus 5 | $0.00036 | $0.00258 |
| Sonnet 5 | $0.00014 | $0.00103 |
| Haiku 4.5 | $0.00007 | $0.00052 |
Grade A, and why
dd-doctor 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 10d 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.
What it actually says
dding-dong doctor
알림이 정상 작동하지 않을 때 원인을 분석합니다.
진단 순서
1. 환경 감지
node "${CLAUDE_PLUGIN_ROOT}/scripts/setup-wizard.mjs" detect --cwd "$(pwd)"
결과를 분석하여 플랫폼, 사운드 플레이어, 알림 도구 상태를 확인합니다.
2. 설정 진단
node "${CLAUDE_PLUGIN_ROOT}/scripts/check-config.mjs" --cwd "$(pwd)"
JSON 결과에서 다음을 확인합니다:
setup.completed— 초기 셋업 완료 여부 (미완료 시/dding-dong:dd-setup권장)config— 병합된 설정 (enabled,sound.events,notification.events등)paths— 각 설정 파일의 경로와 존재 여부
3. 설정 검증
node "${CLAUDE_PLUGIN_ROOT}/scripts/setup-wizard.mjs" validate --cwd "$(pwd)"
자동 검증 항목:
- JSON 파싱 오류
- 필수 키 누락 또는 타입 오류
- 알 수 없는 이벤트 타입
- 사운드 팩 파일 존재 여부
4. 테스트 알림 실행
node "${CLAUDE_PLUGIN_ROOT}/scripts/notify.mjs" test task.complete
5. 진단 결과 요약
발견된 문제와 해결 방법을 한국어로 정리하여 보고합니다:
- 환경 문제 (플레이어/알림도구 미설치)
- 설정 문제 (비활성화, 이벤트 OFF)
- 파일 문제 (사운드 파일 누락)
- 권한 문제 (실행 권한 부족)
관련 스킬
- 초기 설정 →
/dding-dong:dd-setup - 피드백 제출 →
/dding-dong:dd-feedback - 전체 기능 안내 →
/dding-dong:dd-help
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.
- 10d ago First seen · 64 lines · 72 tokens per session scan A 8ea109f53baf
dd-doctor is a skill published in the GitHub repository CaesiumY/dding-dong (2 stars, last pushed 6mo ago), licensed MIT. It adds 72 tokens to every session and 516 once invoked, about $0.0004 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 skills, from other repositories
wsl-vscode-doctor
Diagnose and fix code . failing to launch, or opening a disconnected Windows-side VS Code instead of a WSL-connected (Remote-WSL) window, in a herdr-spawned WSL shell.
investigate-bug-report
Investigate a reported bug to its root cause — reproduce, trace the code path, identify the defect with evidence, assess blast radius, and propose fix candidates without changing code. Use when the user reports or pastes a bug/defect/unexpected behavior and wants it diagnosed, or asks "why is X happening".
opencode-log-investigation
Investigates OpenCode runtime errors by locating and analyzing log files. Use when OpenCode fails to start, plugins do not load, MCP servers error out, or terminal shows cryptic errors without details.
codebase-design
Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.
tidewave-integration
Tidewave MCP runtime tools — debugging, smoke testing, live state inspection, SQL queries, hex docs. Use when evaluating code in a running Phoenix app.
debug
Interactive debugging workflow with hypothesis-driven probe loop. Use when: unknown bugs, script errors, silent failures, troubleshooting. Not for: known bugs (use bug-fix), GitHub issue analysis (use issue-analyze), code understanding (use code-explore). Output: debug report with probe journal + root cause + fix.