mindroom: Agent for Claude Code

.claude/agents/mindroom-tester.md

mindroom-tester is an agent for Claude Code from mindroom-ai/mindroom. It costs 44 tokens per session (5,710 once invoked), scanned A, original, Apache-2.0.

A testing specialist for MindRoom agents that simulates realistic user interactions. MindRoom is the project this agent tests, including its configuration, rooms, commands, and collaboration behavior.

In plain words
What is it for?
Use it to validate MindRoom agent behavior, direct messages, room interactions, commands, schedules, widgets, and multi-agent collaboration. It also verifies the local testing environment before starting.
Why use it?
It checks whether agents respond and work together as expected instead of relying only on code inspection. It begins by reading the project’s instructions and configuration so tests match the actual setup.

Agent for Claude Code

Written for Claude Code: installed under .claude/. Also seen: reads .claude/ paths; names the TodoWrite tool; mentions AGENTS.md.

This is mindroom-ai/mindroom's own configuration. It tells Claude Code how to work on mindroom itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything mindroom configures →

Reuse

Borrowing it

Nothing to install: this file belongs to mindroom-ai/mindroom. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/mindroom-ai/mindroom/main/.claude/agents/mindroom-tester.md
Clone the repo
git clone --depth 1 https://github.com/mindroom-ai/mindroom

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 mindroom-tester

README.md
[![agentmods](https://agentmods.dev/badge/agents/mindroom-ai/mindroom/mindroom-tester/github.svg)](https://agentmods.dev/agents/mindroom-ai/mindroom/mindroom-tester)
Your own site
<a href="https://agentmods.dev/agents/mindroom-ai/mindroom/mindroom-tester"><img src="https://agentmods.dev/badge/agents/mindroom-ai/mindroom/mindroom-tester/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 mindroom-tester

Your own site · 80×15
<a href="https://agentmods.dev/agents/mindroom-ai/mindroom/mindroom-tester"><img src="https://agentmods.dev/badge/agents/mindroom-ai/mindroom/mindroom-tester.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 44 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 5,710 The whole file, excluding the scripts and references it only reads on demand.
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.
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.00044 $0.05710
Opus 5.5 $0.00018 $0.02284
Sonnet 5.5 $0.00009 $0.01142
Haiku 4.5 $0.00004 $0.00571

Measured 17d ago against content hash fcf1b1bc92fb, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

mindroom-tester 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 17d 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/agents/mindroom-tester.md · 673 lines

How it starts

The opening of the file, as written. The whole thing — 673 lines — stays where its author put it; the contents beside it link to each section on GitHub.

You are a MindRoom Testing Specialist that simulates realistic user interactions to systematically test and evaluate MindRoom AI agents. Your primary role is to act as a user would, engaging with agents through the Matty CLI to gather data on their behavior, performance, and collaboration patterns.

MANDATORY INITIALIZATION

BEFORE ANY TESTING, you MUST complete these steps in order:

  1. Read the complete README.md

    cat README.md
    

    Pay special attention to:

    • "How Agents Work" section (response rules, threading behavior)
    • Available commands (discover current commands with !help or src/mindroom/commands/parsing.py)
    • Agent collaboration patterns
    • Direct message behavior
  2. Read AGENTS.md for development context

    cat AGENTS.md
    

    This provides crucial context about the project structure; the live-run and Matty procedures are in .claude/skills/live-test/references/core-mindroom.md.

  3. Inspect config.yaml for agent configurations

    cat config.yaml
    

    Understand:

    • Which agents are configured
    • What tools each agent has access to
    • Model configurations
    • Room assignments
  4. Verify environment setup

    source .venv/bin/activate
    matty rooms
    matty users "Lobby"  # or appropriate room
    

CRITICAL: MindRoom Agent Interaction Rules

Before starting ANY test, you MUST understand these fundamental rules from the MindRoom README:

How MindRoom Agents Work:

  1. Threads are the default - Check !thread_mode show, then the agent's thread_mode and room_thread_modes; room mode delivers replies in the main room
  2. Mentioned agents always respond - Use @mentions to trigger specific agents
  3. Single agent continues - If one agent is in a thread, it keeps responding
  4. Multiple agents collaborate - They work together when multiple are mentioned
  5. Smart routing - System automatically picks the best agent for new threads
  6. Mentioned agents respond - Mention agents with @ to get their responses

Read the full file on GitHub · 673 lines

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. 17d ago Changed fcf1b1bc92fb
  2. 22d ago Changed d3c67f6d89a7
  3. 1mo ago Changed · +5 lines 4df5c571f37c
  4. 1mo ago First seen · 668 lines · 44 tokens per session scan A 6604350eb2e7

Subscribe to this mod's changes

mindroom-tester is an agent published in the GitHub repository mindroom-ai/mindroom (346 stars, last pushed today), licensed Apache-2.0. It adds 44 tokens to every session and 5,710 once invoked, about $0.0002 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.

Related

Other agents, from other repositories

gan-evaluator

GAN Harness — Evaluator agent. Tests the live running application via Playwright, scores against rubric, and provides actionable feedback to the Generator.

affaan-m/ECC · 32 tokens

e2e-runner

End-to-end testing specialist using Vercel Agent Browser (preferred) with Playwright fallback. Use PROACTIVELY for generating, maintaining, and running E2E tests. Manages test journeys, quarantines flaky tests, uploads artifacts (screenshots, videos, traces), and ensures critical user flows work.

affaan-m/ECC · 69 tokens

tdd-guide

Test-Driven Development specialist enforcing write-tests-first methodology. Use PROACTIVELY when writing new features, fixing bugs, or refactoring code. Ensures 80%+ test coverage.

affaan-m/ECC · 42 tokens

ui-tester

Use this agent when the user explicitly requests UI testing, interface validation, or browser-based inspection tasks. This agent is specifically designed to operate Chrome DevTools MCP Server in isolation to prevent context pollution in the main agent.\n\nExamples:\n\n \nContext: User wants to verify that a new…

pchalasani/claude-code-tools · 0 tokens

integration-testing-orchestrator

Use this agent when you need to coordinate end-to-end testing across multiple components, optimize build systems, validate deployments, or ensure proper integration between eBPF programs, Rust collector, and frontend components. Examples: Context: User has made changes to both eBPF programs and Rust collector and…

eunomia-bpf/agentsight · 0 tokens

visual-qa-subagent

Performs visual QA inspection using Playwright browser automation.

closedloop-ai/claude-plugins · 17 tokens