rlm-chunk-analyzer

rlm-chunk-analyzer is an agent for Claude Code from zircote-plugins/claude-team-orchestration. It costs 43 tokens per session (1,523 once invoked), scanned A, original, MIT.

A focused helper for analyzing one section of a large file in an RLM, or Recursive Language Model, workflow. It reads a specified line range and returns structured findings for logs, documentation, configuration, markup, and other non-specialized content.

In plain words
What is it for?
Use it to inspect selected file sections, answer a question about those sections, and report findings for later combination by a coordinating agent.
Why use it?
It lets a larger file be examined in manageable pieces when the whole file will not fit in one context window. It also keeps each chunk's analysis focused and consistently formatted.

Agent for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: model in frontmatter; mentions subagents.

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

Good fit Use it to inspect selected file sections, answer a question about those sections, and report findings for later combination by a coordinating agent.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/zircote-plugins/claude-team-orchestration/rlm-chunk-analyzer
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/zircote-plugins/claude-team-orchestration

Made for: Claude Code.

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-chunk-analyzer

README.md
[![agentmods](https://agentmods.dev/badge/agents/zircote-plugins/claude-team-orchestration/rlm-chunk-analyzer.svg)](https://agentmods.dev/agents/zircote-plugins/claude-team-orchestration/rlm-chunk-analyzer)
Your own site
<a href="https://agentmods.dev/agents/zircote-plugins/claude-team-orchestration/rlm-chunk-analyzer"><img src="https://agentmods.dev/badge/agents/zircote-plugins/claude-team-orchestration/rlm-chunk-analyzer.svg" alt="Measured on agentmods" height="20"></a>
Per session 43 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,523 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.00043 $0.01523
Opus 5 $0.00022 $0.00762
Sonnet 5 $0.00009 $0.00305
Haiku 4.5 $0.00004 $0.00152

Measured 8d ago against content hash 1d8930298602, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

rlm-chunk-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 8d 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-chunk-analyzer.md · 187 lines

How it starts

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

RLM Chunk Analyzer Agent

You are a focused analysis agent within the RLM (Recursive Language Model) workflow. Your role is to analyze a specific segment of a larger file and return structured findings.

Context

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

You are the general-purpose analyzer. For source code, structured data, or JSON content, specialized analyzers handle those types. You handle: log files, prose/documentation, configuration files, markup, and any content type not covered by a specialist.

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 file to read
  • Start line: Starting line number (1-based)
  • End line: Ending line number (1-based)
  • Chunk index (optional): Your position in the sequence, e.g., "chunk 3 of 10"

Example prompt:

Query: What errors occurred and are there any patterns?
File: /var/log/app/server.log
Start line: 1200
End line: 1400
This is chunk 3 of 10. Lines are in chronological order.

Analysis Process

  1. Parse the query, file path, and line range from your prompt
  2. Read the file chunk using the Read tool with offset and limit parameters:
    Read({ file_path: "<file_path>", offset: <start_line>, limit: <end_line - start_line + 1> })
    
  3. Analyze the content with respect to the query
  4. Extract relevant findings, evidence, and insights
  5. Return structured JSON output

Output Format

Always return a JSON object with this structure:

{
  "file_path": "<file_path>",
  "start_line": 1200,
  "end_line": 1400,
  "relevant": true,
  "findings": [
    {
      "type": "finding_type",
      "summary": "Brief description",
      "evidence": "Short quote or reference (max 100 chars)",
      "line": 42
    }
  ],
  "metadata": {
    "content_type": "log|code|prose|data",
    "key_topics": ["topic1", "topic2"]
  }
}

Read the full file on GitHub · 187 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. 8d ago First seen · 187 lines · 43 tokens per session scan A 1d8930298602

Subscribe to this mod's changes

rlm-chunk-analyzer is an agent published in the GitHub repository zircote-plugins/claude-team-orchestration (14 stars, last pushed today), licensed MIT. It adds 43 tokens to every session and 1,523 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.