dding-dong: Instructions file for Claude Code

CLAUDE.md

dding-dong CLAUDE.md is an instructions file for Claude Code from CaesiumY/dding-dong. It costs 1,666 tokens per session, scanned A, original, MIT.

Project instructions for dding-dong, a Claude Code notification plugin that plays sounds and sends operating-system alerts when tasks finish, fail, or need input.

In plain words
What is it for?
Use them when developing or maintaining dding-dong, especially for notification testing, sound-pack changes, configuration checks, version updates, and releases.
Why use it?
They explain the commands needed to test notifications, manage sounds, detect the platform, and check configuration.

Instructions file for Claude Code

Written for Claude Code: the file is CLAUDE.md. Also seen: mentions subagents; mentions Claude Code.

This is CaesiumY/dding-dong's own configuration. It tells Claude Code how to work on dding-dong 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 dding-dong configures →

Reuse

Borrowing it

Nothing to install: this file belongs to CaesiumY/dding-dong. 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/CaesiumY/dding-dong/main/CLAUDE.md
Clone the repo
git clone --depth 1 https://github.com/CaesiumY/dding-dong

Made for: Claude Code.

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 dding-dong CLAUDE.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/caesiumy/dding-dong/claude-md.svg)](https://agentmods.dev/instructions/caesiumy/dding-dong/claude-md)
Your own site
<a href="https://agentmods.dev/instructions/caesiumy/dding-dong/claude-md"><img src="https://agentmods.dev/badge/instructions/caesiumy/dding-dong/claude-md.svg" alt="Measured on agentmods" height="20"></a>
Per session 1,666 This file is loaded in full into every session.
When invoked 1,666 The same file — it is already loaded in full.
Security scan A 1 finding. 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.1 $0.01666 $0.01666
Opus 5 $0.00833 $0.00833
Sonnet 5 $0.00333 $0.00333
Haiku 4.5 $0.00167 $0.00167

Measured 6d ago against content hash 5a50e7118eec, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

dding-dong CLAUDE.md scanned grade A with 1 finding 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 6d 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.

Runs shell commandslowCapability

Expected in a hook, worth knowing in a rule or an instructions file.

- **No npm dependencies**: Only Node.js built-in modules (`node:fs`, `node:path`, `node:child_process`, `node:os`, `node:url`).
CLAUDE.md · 114 lines

How it starts

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

dding-dong

Claude Code notification plugin. Plays sounds and sends OS notifications on task completion, errors, and input requests. Zero npm dependencies — uses only Node.js built-in modules.

Development Commands

# Test notifications (cycles through all event types)
node scripts/notify.mjs test

# Regenerate default sound pack WAV files
node scripts/generate-sounds.mjs

# Detect platform, audio player, and notifier
node scripts/setup-wizard.mjs detect

# Validate config files (JSON parsing, required keys, sound pack existence)
node scripts/setup-wizard.mjs validate

# Sound pack management (discover, validate, create, clone, apply)
node scripts/pack-wizard.mjs discover

# Version sync (plugin.json → marketplace.json)
node scripts/sync-version.mjs sync
node scripts/sync-version.mjs verify
node scripts/sync-version.mjs bump patch   # or minor, major

# Release (creates git tag + pushes → GitHub Actions creates release)
node scripts/release.mjs            # Create git tag and push
node scripts/release.mjs --dry-run  # Preview without creating tag

# Website (pnpm required — do NOT use npm/yarn)
cd website && pnpm install    # Install dependencies
cd website && pnpm dev        # Dev server (auto-copies sound files)
cd website && pnpm build      # Production build

Design Rules

  • Simplicity First: Make every change as simple as possible. Impact minimal code.
  • Root cause fixes: Find root causes. No temporary fixes. Senior developer standards.
  • Minimal impact: Changes should only touch what's necessary. Avoid introducing bugs.
  • Stop hook MUST respond: stop.mjs must write {} (empty JSON object) to stdout. Missing this halts Claude execution.
  • Always exit(0) on error: Notification failure must never block Claude. All hook catch blocks call process.exit(0).
  • detached + unref: Audio processes use spawn(..., { detached: true, stdio: 'ignore' }).unref() to complete within the 5-second hook timeout.
  • ESM only: All scripts use .mjs extension with import/export syntax.
  • No npm dependencies: Only Node.js built-in modules (node:fs, node:path, node:child_process, node:os, node:url).

Read the full file on GitHub · 114 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. 6d ago First seen · 114 lines · 1,666 tokens per session scan A 5a50e7118eec

Subscribe to this mod's changes

dding-dong CLAUDE.md is an instructions file published in the GitHub repository CaesiumY/dding-dong (2 stars, last pushed 6mo ago), licensed MIT. It adds 1,666 tokens to every session, about $0.0083 per session on Opus 5. A static security scan graded it A with 1 finding (runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other instructions, from other repositories

next.js AGENTS.md

AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js · 7,296 tokens

codex AGENTS.md

AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.

openai/codex · 5,182 tokens

vscode buildNext.instructions.md

Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).

microsoft/vscode · 6,785 tokens

vscode oss-third-party-notices.instructions.md

Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).

microsoft/vscode · 5,001 tokens

langchain AGENTS.md

AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.

langchain-ai/langchain · 4,469 tokens

spec-kit AGENTS.md

AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.

github/spec-kit · 7,104 tokens