Borrowing it
Nothing to install: this file belongs to noisy/noisy-coding. 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/noisy/noisy-coding/main/CLAUDE.mdgit clone --depth 1 https://github.com/noisy/noisy-codingWrote 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/instructions/noisy/noisy-coding/claude-md)<a href="https://agentmods.dev/instructions/noisy/noisy-coding/claude-md"><img src="https://agentmods.dev/badge/instructions/noisy/noisy-coding/claude-md/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/instructions/noisy/noisy-coding/claude-md"><img src="https://agentmods.dev/badge/instructions/noisy/noisy-coding/claude-md.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.00865 | $0.00865 |
| Opus 5.5 | $0.00346 | $0.00346 |
| Sonnet 5.5 | $0.00173 | $0.00173 |
| Haiku 4.5 | $0.00086 | $0.00086 |
Grade B, and why
noisy-coding CLAUDE.md scanned grade B with 2 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.
Sends data to an external URLmediumData exfiltration
A POST to an outside endpoint may be telemetry or may be exfiltration; either way the mod talks to somewhere, and you should know where.
curl -X POST http://127.0.0.1:7765/shutdown -d '{"delay_seconds":60}' Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s http://127.0.0.1:8765/status | grep -o '"version": "[^"]*"' How it starts
The opening of the file, as written. The whole thing — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
noisy-coding — agent notes
Voice coding for Claude Code: a daemon (production runs in Docker) plus Claude
Code hooks and an MCP server. Python backend in src/noisy_coding/, Vue
dashboard in dashboard/, hooks in hooks/.
Local development setup
Follow docs/local-development.md — do not improvise. In short: production
owns ports 8765–8767; the dev instance from this checkout runs on 7765
(scripts/dev_daemon.sh). Wiring a session to dev means BOTH:
- a second MCP server named
noisy-coding-dev(stdio, LOCAL scope — oneclaude mcp add --scope localper machine; NEVER commit it to a.mcp.json, the plugin auto-ships that file to end users), and - project-scoped hook overrides in this repo's
.claude/settings.jsonpointing at localhooks/*.pywithNOISY_CODING_LISTENER_PORT=7765. These DUPLICATE the global docker-exec hooks on purpose — global ones keep serving production, project ones serve dev.
Key docs
docs/hooks.md— the five hooks, why each exists, registration pathsdocs/ports.md— what each port is fordocs/local-development.md— dev instance next to production
Releasing
Run python3 scripts/bump_version.py X.Y.Z - it bumps all four version
files AND prints the release checklist. Follow it to the letter; the one
step agents keep forgetting: auto-generated release notes only list PRs
and miss direct commits - always write real notes (highlights for
humans) and publish with gh release edit vX.Y.Z --notes-file ... --draft=false,
then verify the GitHub release and the Docker image manifest.
Deploying to the local prod container is part of the release:
docker compose pull && docker compose up -d
curl -s http://127.0.0.1:8765/status | grep -o '"version": "[^"]*"'
The curl MUST report the version just released - up -d alone proves
nothing. docker-compose.yml runs the PUBLISHED image; never point it at
build: (a stale local build once shadowed a release as 2.13.4) - the
working tree runs via docker-compose.dev.yml under a distinct name.
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.
- 1mo ago First seen · 75 lines · 865 tokens per session scan B 87f9fb795d53
noisy-coding CLAUDE.md is an instructions file published in the GitHub repository noisy/noisy-coding (9 stars, last pushed 1mo ago), licensed MIT. It adds 865 tokens to every session, about $0.0035 per session on Opus 5.5. A static security scan graded it B with 2 findings (sends data to an external url, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other instructions, from other repositories
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).
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.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.