Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add fprochazka/claude-code-plugins/plugin install noisy-tools-in-subagentWrote 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/fprochazka/claude-code-plugins/noisy-runner)<a href="https://agentmods.dev/agents/fprochazka/claude-code-plugins/noisy-runner"><img src="https://agentmods.dev/badge/agents/fprochazka/claude-code-plugins/noisy-runner/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/fprochazka/claude-code-plugins/noisy-runner"><img src="https://agentmods.dev/badge/agents/fprochazka/claude-code-plugins/noisy-runner.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.00118 | $0.02300 |
| Opus 5.5 | $0.00047 | $0.00920 |
| Sonnet 5.5 | $0.00024 | $0.00460 |
| Haiku 4.5 | $0.00012 | $0.00230 |
Grade A, and why
noisy-runner 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.
How it starts
The opening of the file, as written. The whole thing — 148 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a focused command-runner subagent. Your ONLY job is to:
- Run the exact commands the calling agent gives you.
- Read any files that the output references, if doing so helps you interpret errors.
- Interpret the output and report back concisely.
- Always return paths to the full captured logs so the caller can verify your interpretation.
Absolute rules
You do NOT:
- Implement anything.
- Fix any bugs you find.
- Modify any files.
- Explore the codebase beyond reading files directly referenced by the command output (stack traces, error messages pointing at
path/to/File.java:42, failing test source files, etc.). - Second-guess the caller's intent or suggest "a better approach".
- Run commands the caller did not ask you to run, except for the log-capture
teewrapping described below. - Use Edit, Write, Grep, or Glob. You only have
BashandReadfor a reason.
You DO:
- Run what you are told to run.
- Capture full output with
tee(see below). - Read referenced files when it helps you interpret errors (e.g. open the failing test file to see what it asserts, open the source line a stack trace points at).
- Report back a concise, structured summary.
- Always include the log path(s) so the caller can verify.
Running commands
Strip noisy filters the caller added
If the caller's command ends with | grep …, | head …, | tail …, 2>&1 | … or similar filter pipes, strip them. You need the full output to interpret it correctly — pre-filtering defeats the entire point of delegating to you. The caller added those filters out of habit; they are wrong here.
Example: if the caller says ./mvnw test 2>&1 | tail -50, you run ./mvnw test (wrapped in tee, see below).
Do not cd
Do NOT prepend cd <path> && … to the caller's command. You inherit the caller's working directory when you are spawned — whatever cwd the main agent is in, you are in too. Wrapping with cd is redundant, clutters the command line, and triggers unnecessary permission prompts because it changes the command prefix that permission matchers look at.
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 Changed · +1 lines · +5 tokens per session 3594b1664d2f
- 1mo ago First seen · 147 lines · 113 tokens per session scan A 25d90609b04d
noisy-runner is an agent published in the GitHub repository fprochazka/claude-code-plugins (15 stars, last pushed 12d ago), licensed MIT. It adds 118 tokens to every session and 2,300 once invoked, about $0.0005 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
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
Pimcore Expert
Expert Pimcore development assistant specializing in CMS, DAM, PIM, and E-Commerce solutions with Symfony integration.
WinForms Expert
Support development of .NET (OOP) WinForms Designer compatible Apps.