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.
npx agentmods add agents/zircote-plugins/claude-team-orchestration/rlm-data-analyzergit clone --depth 1 https://github.com/zircote-plugins/claude-team-orchestrationWrote 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/zircote-plugins/claude-team-orchestration/rlm-data-analyzer)<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>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.00044 | $0.01511 |
| Opus 5 | $0.00022 | $0.00756 |
| Sonnet 5 | $0.00009 | $0.00302 |
| Haiku 4.5 | $0.00004 | $0.00151 |
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.
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
- Parse the query, file path, and any column hints from your prompt
- Read the chunk file using the Read tool
- Identify the header row and understand column structure
- 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
- 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"]
}
}
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.
- 5d ago First seen · 163 lines · 44 tokens per session scan A 3db38969dc1b
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.
Other agents, from other repositories
plan_mode_first_entry_reminder
Agent "plan_mode_first_entry_reminder" from GCWing/BitFun, covering plan workflow, asking user questions in plan mode, plan creation and updates, delegation and plan writing guidelines.
explore_agent
You are a read-only codebase exploration agent for BitFun (an AI IDE). Given the user's message, use the available tools to search and analyze existing code. Do what has been asked; nothing more, nothing less. When you complete the task simply respond with a detailed writeup.
Knowledge
Structures codebase exploration into a feature knowledge base and registers it in the index cache.
Validate
Dedicated agent for running validation commands (build, typecheck, lint, test). Reports pass/fail with structured failure details - never fixes.
claude-deep-review
Internal Claude subagent for deep code review — security vulnerabilities, bug detection, and performance analysis. Has native codebase access (Read, Grep, Glob, Bash) to trace input paths, follow call chains, profile hot paths, and verify assumptions. Launched automatically by council review workflows — not invoked…
silent-failure-hunter
Error handling review agent for CI: identifies silent failures, empty catch blocks, swallowed errors, overly broad exception handling, and missing user feedback in PR diffs.