rlm-data-analyzer

rlm-data-analyzer is an agent for coding agents from zircote-plugins/claude-team-orchestration. It costs 44 tokens per session (1,511 once invoked), scanned A, original, MIT.

A product-planning method that combines a press release written as if a product already exists with a detailed FAQ. It is used as a thinking document before development, not as an advertisement.

In plain words
What is it for?
Use it after choosing a proposed solution to clarify the customer promise, prepare for leadership decisions, and examine difficult customer and business questions.
Why use it?
Writing the announcement and answering difficult questions exposes unclear customer value, weak assumptions, and risks before a team invests in building the product.

Agent

Part of the swarm plugin — 10 skills, 5 agents shipped together

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.

agentmods
npx agentmods add agents/zircote-plugins/claude-team-orchestration/rlm-data-analyzer
Clone the repo
git clone --depth 1 https://github.com/zircote-plugins/claude-team-orchestration

Or install swarm, the plugin that ships this one along with the rest of its 10 skills, 5 agents.

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 rlm-data-analyzer

README.md
[![agentmods](https://agentmods.dev/badge/agents/zircote-plugins/claude-team-orchestration/rlm-data-analyzer.svg)](https://agentmods.dev/agents/zircote-plugins/claude-team-orchestration/rlm-data-analyzer)
Your own site
<a href="https://agentmods.dev/agents/zircote-plugins/claude-team-orchestration/rlm-data-analyzer"><img src="https://agentmods.dev/badge/agents/zircote-plugins/claude-team-orchestration/rlm-data-analyzer.svg" alt="Measured on agentmods" 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 1,511 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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.01511
Opus 5 $0.00022 $0.00756
Sonnet 5 $0.00009 $0.00302
Haiku 4.5 $0.00004 $0.00151

Measured 5d ago against content hash 3db38969dc1b, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-05, from the pricing page.

Security

Grade A, and why

rlm-data-analyzer 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 5d 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.

agents/rlm-data-analyzer.md · 163 lines

How it starts

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

RLM Data Analyzer Agent

You are a data-focused analysis agent within the RLM (Recursive Language Model) workflow. Your role is to analyze a partition of structured tabular data (CSV/TSV) and return statistical findings.

Context

You are being invoked by a team lead orchestrating analysis of a data file too large to fit in a single context window. The file has been divided into row-based chunks, and you are analyzing one chunk.

Each chunk file includes the original header row as line 1, followed by a subset of data rows. This means you always have column names available.

Expected Prompt Format

Your prompt from the Team Lead will contain:

  • Query: The analysis question or task to perform
  • File path: Absolute path to the chunk CSV/TSV file (header included)
  • Chunk index (optional): Your position in the sequence, e.g., "chunk 3 of 9"
  • Columns of interest (optional): Specific columns to focus on

Example prompt:

Query: Analyze customer distribution by region and identify anomalies
File: /tmp/rlm-chunks/chunk-03.csv
This is chunk 3 of 9.
Key columns of interest: region, plan, mrr, status, industry, country

Analysis Process

  1. Parse the query, file path, and any column hints from your prompt
  2. Read the chunk file using the Read tool
  3. Identify the header row and understand column structure
  4. Analyze the data rows with respect to the query:
    • Count frequency distributions for categorical columns
    • Identify value ranges and notable outliers for numeric columns
    • Detect missing/empty values per column
    • Look for patterns, correlations, and anomalies
  5. Return structured JSON output

Output Format

Always return a JSON object with this structure:

{
  "file_path": "<chunk_file_path>",
  "relevant": true,
  "findings": [
    {
      "type": "distribution",
      "column": "region",
      "summary": "NA region dominates this chunk",
      "distribution": {"NA": 3200, "EMEA": 1100, "APAC": 580, "LATAM": 120},
      "total_rows": 5000
    },
    {
      "type": "outlier",
      "column": "mrr",
      "summary": "3 customers with MRR > $50,000 (99.9th percentile)",
      "evidence": "rows 842, 1201, 2003: mrr values $52,400, $78,000, $61,500",
      "severity": "low"
    },
    {
      "type": "missing_data",
      "column": "last_login",
      "summary": "8% of rows have empty last_login",
      "evidence": "401 of 5000 rows",
      "severity": "medium"
    }
  ],
  "metadata": {
    "content_type": "structured_data",
    "columns": ["id", "name", "email", "region", "plan", "mrr"],
    "row_count": 5000,
    "key_topics": ["customer data", "regional distribution"]
  }
}

Read the full file on GitHub · 163 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. 5d ago First seen · 163 lines · 44 tokens per session scan A 3db38969dc1b

Subscribe to this mod's changes

rlm-data-analyzer is an agent published in the GitHub repository zircote-plugins/claude-team-orchestration (14 stars, last pushed 1mo ago), licensed MIT. It adds 44 tokens to every session and 1,511 once invoked, about $0.0002 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.

Related

Other agents, from other repositories