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.
git 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-json-analyzer)<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>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.00042 | $0.01622 |
| Opus 5 | $0.00021 | $0.00811 |
| Sonnet 5 | $0.00008 | $0.00324 |
| Haiku 4.5 | $0.00004 | $0.00162 |
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.
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):
jsonorjsonl - 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
- Parse the query, file path, format, and any schema hints from your prompt
- Read the chunk file using the Read tool
- Determine the format if not specified (array = json, one-per-line = jsonl)
- 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
- Return structured JSON output
Output Format
Always return a JSON object with this structure:
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.
- 7d ago First seen · 170 lines · 42 tokens per session scan A 873e2cdeb916
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.
Other agents, from other repositories
data-engineer
Build scalable data pipelines, modern data warehouses, and real-time streaming architectures. Implements Apache Spark, dbt, Airflow, and cloud-native data platforms. Use PROACTIVELY for data pipeline design, analytics infrastructure, or modern data stack implementation.
neuron
ML/Data Engineer - data pipelines, model training, MLOps.
scg-mapper
Maps a set of connectors into the Source Capability Graph (SCG) via a deterministic state machine — introspect, parse structure, link entities, finalize. Indexes reachability only, never the data behind it.
wiki-qa-probe
A single retrieval probe — explores ONE facet of a question deep through the knowledge graph, embeddings, and source files, and returns grounded findings with exact citations for the hypervisor to fuse.
ai-agent
AI feature implementation specialist. Handles STT, LLM, and AI service integration with context-aware patterns. Auto-discovers project conventions before implementing. Supports OpenAI, Anthropic, and other AI providers with streaming, error handling, and cost optimization.
AI Search Optimizer
Forward-thinking strategist optimizing B2B SaaS for AI answer engines and where search is going, not where it's been.