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.
git clone --depth 1 https://github.com/Madhan230205/token-reducerWrote 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/madhan230205/token-reducer/noise-chunker)<a href="https://agentmods.dev/agents/madhan230205/token-reducer/noise-chunker"><img src="https://agentmods.dev/badge/agents/madhan230205/token-reducer/noise-chunker.svg" alt="Measured on agentmods" 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.00025 | $0.00101 |
| Opus 5 | $0.00013 | $0.00051 |
| Sonnet 5 | $0.00005 | $0.00020 |
| Haiku 4.5 | $0.00003 | $0.00010 |
Grade A, and why
noise-chunker 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 8d 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
You are a preprocessing specialist.
- Remove repetitive, boilerplate, and low-signal lines.
- Preserve meaningful technical statements and code semantics.
- Chunk data into stable windows with overlap.
- Return source, chunk index, and estimated tokens.
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.
- 8d ago First seen · 15 lines · 25 tokens per session scan A 1ae0b5052b2d
noise-chunker is an agent published in the GitHub repository Madhan230205/token-reducer (44 stars, last pushed 4mo ago), licensed MIT. It adds 25 tokens to every session and 101 once invoked, about $0.0001 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-30.
Other agents, from other repositories
langchain-expert
Use this agent when you need expert LangChain development with focus on LCEL, LangGraph, RAG pipelines, and multi-agent systems. This agent specializes in LangChain Python/TypeScript, chain composition, vector databases, embeddings, and building production-ready LLM applications. Examples: Context: User needs to build…
mlops
ML infrastructure specialist — training pipelines, model serving, GPU optimization, distributed training, and reproducible environments.
data-scientist
Data analysis and pipeline specialist — EDA, feature engineering, data quality, bias auditing, and dataset documentation.
experiment-runner
ML experiment design specialist — ablation studies, hyperparameter search, reproducibility, statistical rigor, and result analysis.
ai-engineer
Build production-ready LLM applications, advanced RAG systems, and intelligent agents. Implements vector search, multimodal AI, agent orchestration, and enterprise AI integrations. Use PROACTIVELY for LLM features, chatbots, AI agents, or AI-powered applications.
koshi-librarian
Use proactively when the user wants to index code or documentation and search it with Koshi's BM25 retrieval. Specializes in corpus management — indexing directories, inspecting indexed sources, and running keyword searches. Does NOT manage memories, compile context windows, or score teams.