noisy-tools-in-subagent

noisy-tools-in-subagent is a plugin for Claude Code from fprochazka/claude-code-plugins. Its manifest loads nothing; the 1 agent it bundles cost 118 tokens per session together, scanned A, original, MIT.

A plugin that sends output-heavy commands, such as builds, tests, linters, and code analysis, to a secondary AI agent. A linter is a tool that checks code for likely mistakes or style problems.

In plain words
What is it for?
Use it when running builds, tests, linters, or static analysis that produce large amounts of output. Specific agent types can be exempted from delegation.
Why use it?
It keeps long command output out of the main agent's conversation context, leaving more room for the actual task and decisions.

Plugin for Claude Code

Written for Claude Code: a Claude Code plugin manifest. Also seen: mentions subagents.

Good fit Use it when running builds, tests, linters, or static analysis that produce large amounts of output. Specific agent types can be exempted from delegation.

Compare 6 plugins from other repositories ↓
Install in Claude Code
/plugin marketplace add fprochazka/claude-code-plugins
/plugin install noisy-tools-in-subagent
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.

Clone the repo
git clone --depth 1 https://github.com/fprochazka/claude-code-plugins

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 noisy-tools-in-subagent

README.md
[![agentmods](https://agentmods.dev/badge/plugins/fprochazka/claude-code-plugins/noisy-tools-in-subagent/github.svg)](https://agentmods.dev/plugins/fprochazka/claude-code-plugins/noisy-tools-in-subagent)
Your own site
<a href="https://agentmods.dev/plugins/fprochazka/claude-code-plugins/noisy-tools-in-subagent"><img src="https://agentmods.dev/badge/plugins/fprochazka/claude-code-plugins/noisy-tools-in-subagent/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.

agentmods 80×15 button for noisy-tools-in-subagent

Your own site · 80×15
<a href="https://agentmods.dev/plugins/fprochazka/claude-code-plugins/noisy-tools-in-subagent"><img src="https://agentmods.dev/badge/plugins/fprochazka/claude-code-plugins/noisy-tools-in-subagent.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session not measured What this adds to a session before it is invoked.
When invoked not measured The manifest loads nothing itself; its 1 agent cost 118 tokens a session between them.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Security

Grade A, and why

noisy-tools-in-subagent 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 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.

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.

plugins/noisy-tools-in-subagent/.claude-plugin/plugin.json · 27 lines

What it actually says

{
  "$schema": "https://anthropic.com/claude-code/plugin.schema.json",
  "name": "noisy-tools-in-subagent",
  "version": "0.6.0",
  "description": "Forces noisy commands (builds, tests, linters, static analysis) to run inside a Sonnet subagent instead of the main context, preserving main-agent tokens",
  "author": {
    "name": "Filip Procházka",
    "url": "https://github.com/fprochazka"
  },
  "license": "MIT",
  "homepage": "https://github.com/fprochazka/claude-code-plugins/tree/master/plugins/noisy-tools-in-subagent",
  "userConfig": {
    "exempt_agent_types": {
      "type": "string",
      "multiple": true,
      "title": "Exempt agent types",
      "description": "Agent types allowed to run noisy commands directly. Use for agents that cannot delegate, because their definition omits the Agent tool or they run at the subagent nesting limit. Each entry is a regex that must match the whole agent type, for example my-plugin:leaf-worker."
    }
  },
  "dependencies": [
    {
      "name": "bash-classify-hook",
      "marketplace": "fprochazka-bash-classify"
    }
  ]
}
Contents

What it installs

The manifest is a name and a version. 1 agent travel with it, and installing the plugin installs all of them — 118 tokens a session between them. Each is measured on its own page, and each can be installed alone.

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. 1mo ago Changed b0766cf582c3
  2. 1mo ago First seen · 27 lines scan A 0dc88d46904c

Subscribe to this mod's changes

noisy-tools-in-subagent is a plugin published in the GitHub repository fprochazka/claude-code-plugins (15 stars, last pushed 12d ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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.