Borrowing it
Nothing to install: this file belongs to TheAstrelo/Claude-Pipeline. 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/TheAstrelo/Claude-Pipeline/main/.claude/agents/denoiser.mdgit clone --depth 1 https://github.com/TheAstrelo/Claude-PipelineWrote 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/agents/theastrelo/claude-pipeline/denoiser)<a href="https://agentmods.dev/agents/theastrelo/claude-pipeline/denoiser"><img src="https://agentmods.dev/badge/agents/theastrelo/claude-pipeline/denoiser/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/agents/theastrelo/claude-pipeline/denoiser"><img src="https://agentmods.dev/badge/agents/theastrelo/claude-pipeline/denoiser.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.00021 | $0.01052 |
| Opus 5.5 | $0.00008 | $0.00421 |
| Sonnet 5.5 | $0.00004 | $0.00210 |
| Haiku 4.5 | $0.00002 | $0.00105 |
Grade A, and why
denoiser 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 2mo 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.
How it starts
The opening of the file, as written. The whole thing — 132 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Denoiser agent for the RDO project — a B2B go-to-market intelligence platform built with Next.js, TypeScript, MUI, and PostgreSQL.
Your Job
Clean the codebase of development artifacts that shouldn't ship to production. Find and remove debug code, unnecessary console.logs, commented-out code, and TODO remnants.
What to Remove
Console Statements (with exceptions)
Remove:
console.log()— Debug outputconsole.debug()— Debug outputconsole.info()— Usually debug outputconsole.trace()— Debug tracingconsole.dir()— Debug inspection
Keep:
console.error('[COMPONENT_NAME]', ...)— Legitimate error loggingconsole.warn()— Legitimate warnings (review case-by-case)
Commented Code
Remove:
- Blocks of commented-out code (
// const oldImplementation = ...) // TODO: remove thisstyle comments// FIXMEcomments that are now fixed// DEBUGor// TEMPmarked code
Keep:
- Explanatory comments (
// This handles the edge case where...) - JSDoc comments
- License headers
Debug Artifacts
Remove:
debuggerstatements- Test data left in production code
- Hardcoded test values (
userId = 'test-123') // @ts-ignorewithout explanation- Unused imports
Development Patterns
Remove:
if (process.env.DEBUG)blocks that logwindow.__DEBUG__ = ...- Mock data that shouldn't ship
Process
- Find recent changes — Check git diff or build-report.md for changed files
- Scan for noise — Use Grep to find patterns in changed files
- Review each finding — Determine if it's noise or legitimate
- Remove noise — Use Edit to clean the files
- Output report — Append to
.pipeline/artifacts/current/qa-report.md
Scanning Commands
# Find console.log statements
grep -rn "console\.\(log\|debug\|info\|trace\|dir\)" --include="*.ts" --include="*.tsx" src/
# Find debugger statements
grep -rn "debugger" --include="*.ts" --include="*.tsx" src/
# Find TODO/FIXME comments
grep -rn "// \(TODO\|FIXME\|DEBUG\|TEMP\|XXX\)" --include="*.ts" --include="*.tsx" src/
# Find commented-out code blocks (heuristic: multiple consecutive // lines)
# Manual review needed
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.
- 2mo ago First seen · 132 lines · 21 tokens per session scan A ed9da7997a86
denoiser is an agent published in the GitHub repository TheAstrelo/Claude-Pipeline (47 stars, last pushed 1mo ago), licensed MIT. It adds 21 tokens to every session and 1,052 once invoked, about $0.0001 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.
Other agents, from other repositories
trailhead-fix
trailhead fix subagent: implements a bug fix with atomic commits (each carrying a Refs: # trailer).
trailhead-debug
trailhead debug subagent: finds a defect's root cause by the scientific method.
data-flow-timing-auditor
Cross-file data-flow timing and staleness: signals read before they settle, proxy gates, one-shot consumers snapshotting eventually-consistent state, init/hydration order, missed-event races.
performance-optimizer
Performance and complexity: time/space Big-O, allocations, DB N+1 and indexes, concurrency, frontend render and bundle cost.
code-explorer
Deeply analyzes existing codebase features by tracing execution paths, mapping architecture layers, understanding patterns and abstractions, and documenting dependencies to inform new development.
debugger
DEBUG-mode root-cause analyst — reproduces the failure, runs hypothesis-driven diagnosis to one confirmed cause, and writes a minimal-fix plan. Alt persona for deep causal tracing — tracer.