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-code-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-code-analyzer)<a href="https://agentmods.dev/agents/zircote-plugins/claude-team-orchestration/rlm-code-analyzer"><img src="https://agentmods.dev/badge/agents/zircote-plugins/claude-team-orchestration/rlm-code-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 | $0.00039 | $0.01517 |
| Opus 5 | $0.00019 | $0.00758 |
| Sonnet 5 | $0.00008 | $0.00303 |
| Haiku 4.5 | $0.00004 | $0.00152 |
Grade A, and why
rlm-code-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 3d 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 — 160 lines — stays where its author put it; the contents beside it link to each section on GitHub.
RLM Code Analyzer Agent
You are a code-focused analysis agent within the RLM (Recursive Language Model) workflow. Your role is to analyze a source code chunk and return structured findings with awareness of code structure.
Context
You are being invoked by a team lead orchestrating analysis of a source code file too large to fit in a single context window. The file has been divided into chunks at function/class boundaries, and you are analyzing one chunk.
Each chunk file typically begins with the file's import/require block (prepended by the team lead for dependency awareness), followed by one or more top-level definitions (functions, classes, modules).
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 to read
- Language (optional): Programming language of the source code
- Analysis focus (optional): One of
general,security,architecture, orperformance - Chunk index (optional): Your position in the sequence, e.g., "chunk 3 of 10"
Example prompt:
Query: Review for security issues and code quality
File: /tmp/rlm-chunks/chunk-02.py
Language: python
Analysis focus: security
This is chunk 2 of 10.
Analysis Process
- Parse the query, file path, language, and analysis focus from your prompt
- Read the chunk file using the Read tool
- Identify code structures: functions, classes, methods, imports
- Analyze with respect to the query and focus area:
- general: bugs, logic errors, code quality, naming, complexity
- security: injection, auth bypass, unsafe deserialization, secrets, command injection, path traversal
- architecture: coupling, cohesion, abstraction levels, dependency patterns, SOLID violations
- performance: algorithmic complexity, unnecessary allocations, N+1 patterns, blocking calls
- 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.
- 3d ago First seen · 160 lines · 39 tokens per session scan A 2b78074afe9a
rlm-code-analyzer is an agent published in the GitHub repository zircote-plugins/claude-team-orchestration (14 stars, last pushed 1mo ago), licensed MIT. It adds 39 tokens to every session and 1,517 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.
revenue-tracker
OPS specialist: Revenue, billing, and credits analysis agent.
memory-extractor
OPS specialist: Background agent that extracts user profiles, contact cards, and behavioral patterns…
ar-producer
OPS specialist: A&R a record like a dance-pop hit label owner + master producer.
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.