denoise

denoise is a command for Claude Code from TheAstrelo/Claude-Pipeline. It costs 0 tokens per session (442 once invoked), scanned A, original, MIT.

A command for removing development leftovers from code before it is shipped, such as debug statements, obsolete commented code, and test data.

In plain words
What is it for?
Scanning changed files, cleaning debug output and resolved TODO comments, checking hardcoded test values, and recording the results in a quality-assurance report.
Why use it?
It reduces noise and prevents accidental development artifacts from remaining in production files, while leaving ambiguous findings for review.

Command for Claude Code

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add commands/theastrelo/claude-pipeline/denoise
Clone the repo
git clone --depth 1 https://github.com/TheAstrelo/Claude-Pipeline

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 denoise

README.md
[![agentmods](https://agentmods.dev/badge/commands/theastrelo/claude-pipeline/denoise.svg)](https://agentmods.dev/commands/theastrelo/claude-pipeline/denoise)
Your own site
<a href="https://agentmods.dev/commands/theastrelo/claude-pipeline/denoise"><img src="https://agentmods.dev/badge/commands/theastrelo/claude-pipeline/denoise.svg" alt="Measured on agentmods" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 442 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. 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.00000 $0.00442
Opus 5 $0.00000 $0.00221
Sonnet 5 $0.00000 $0.00088
Haiku 4.5 $0.00000 $0.00044

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

Security

Grade A, and why

denoise 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 5d 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.

.claude/commands/denoise.md · 83 lines

What it actually says

Remove debug artifacts and development leftovers from the build.


Purpose

Clean the codebase of development artifacts that shouldn't ship to production:

  • Console.log statements (except legitimate error logging)
  • Commented-out code blocks
  • TODO/FIXME comments that are resolved
  • Debugger statements
  • Test data left in production code

Execution

Use the denoiser agent.

Input: Read build-report.md to identify changed files (or use git diff if no build report).

Process:

  1. Identify files changed in the build
  2. Scan for noise patterns:
    • console.log/debug/info/trace/dir
    • debugger statements
    • // TODO: remove style comments
    • Blocks of commented-out code
    • Hardcoded test values
  3. For each finding:
    • If clearly noise: remove it
    • If ambiguous: flag for review
  4. Append results to qa-report.md

What to Remove

Pattern Action
console.log() Remove
console.debug() Remove
debugger Remove
// TODO: remove Remove
Commented code blocks Remove
console.error('[Name]', ...) Keep (legitimate logging)
Explanatory comments Keep

Output

After cleaning, report:

## Denoise Complete

**Verdict:** [CLEAN | CLEANED | NEEDS_ATTENTION]

### Summary
- Files scanned: [N]
- Items removed: [N]
- Items kept: [N]
- Items needing review: [N]

### Removed
[List of removed items with file:line references]

### Needs Attention
[Items that might be noise but require human judgment]

### Next Step
Run `/qf` for code quality check.

Gate

This command is part of the QA pipeline. It should be run after /build completes. Order: /denoise/qf/qb/qd/security-review

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. 5d ago First seen · 83 lines · 0 tokens per session scan A da9fbf024c10

Subscribe to this mod's changes

denoise is a command published in the GitHub repository TheAstrelo/Claude-Pipeline (44 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 442 tokens. 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.