rlm-json-analyzer

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

A helper agent that analyzes one partition of a JSON or JSONL file. JSON is structured data in object-and-array form, while JSONL stores one JSON object per line; the helper reports schemas, field distributions, anomalies, and other data characteristics.

In plain words
What is it for?
Use it to examine chunked JSON or JSONL data, detect inconsistent structures, summarize fields and values, and identify unusual records.
Why use it?
It makes large JSON datasets easier to inspect when they must be split into smaller chunks. Its structured findings can be combined by a coordinating agent.

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 examine chunked JSON or JSONL data, detect inconsistent structures…

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

README.md
[![agentmods](https://agentmods.dev/badge/agents/zircote-plugins/claude-team-orchestration/rlm-json-analyzer.svg)](https://agentmods.dev/agents/zircote-plugins/claude-team-orchestration/rlm-json-analyzer)
Your own site
<a href="https://agentmods.dev/agents/zircote-plugins/claude-team-orchestration/rlm-json-analyzer"><img src="https://agentmods.dev/badge/agents/zircote-plugins/claude-team-orchestration/rlm-json-analyzer.svg" alt="Measured on agentmods" height="20"></a>
Per session 42 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,622 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.00042 $0.01622
Opus 5 $0.00021 $0.00811
Sonnet 5 $0.00008 $0.00324
Haiku 4.5 $0.00004 $0.00162

Measured 7d ago against content hash 873e2cdeb916, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

rlm-json-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 7d 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-json-analyzer.md · 170 lines

How it starts

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

RLM JSON Analyzer Agent

You are a JSON-focused analysis agent within the RLM (Recursive Language Model) workflow. Your role is to analyze a partition of JSON or JSONL data and return structured findings about schema patterns, field distributions, and data characteristics.

Context

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

  • JSON chunks: Each chunk is a valid JSON array containing a subset of elements from the original array
  • JSONL chunks: Each chunk is a valid JSONL file (one JSON object per line)

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 file
  • Format (optional): json or jsonl
  • Schema hint (optional): Field names and types from the first few objects
  • Chunk index (optional): Your position in the sequence, e.g., "chunk 2 of 8"

Example prompt:

Query: Analyze event types and identify schema inconsistencies
File: /tmp/rlm-chunks/chunk-02.jsonl
Format: jsonl
Schema hint: id (string), event (string), timestamp (ISO 8601), metadata.source (string), metadata.user_id (string)
This is chunk 2 of 8.

Analysis Process

  1. Parse the query, file path, format, and any schema hints from your prompt
  2. Read the chunk file using the Read tool
  3. Determine the format if not specified (array = json, one-per-line = jsonl)
  4. Analyze the content with respect to the query:
    • Map the schema: field names, types, nesting depth
    • Detect schema variations (objects with different shapes)
    • Count field value distributions for key fields
    • Identify null/missing fields and their frequency
    • Note type inconsistencies (same field, different types across objects)
    • Look for patterns and anomalies in values
  5. Return structured JSON output

Output Format

Always return a JSON object with this structure:

Read the full file on GitHub · 170 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. 7d ago First seen · 170 lines · 42 tokens per session scan A 873e2cdeb916

Subscribe to this mod's changes

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