result-aggregator

result-aggregator is an agent for Claude Code from joseairosa/recall. It costs 19 tokens per session (833 once invoked), scanned A, original, MIT.

An agent that combines and checks results from smaller tasks in Recall's RLM system, a system for splitting work into subtasks. It checks whether the subtasks finished, merges their results, and prepares a final answer.

In plain words
What is it for?
Use it to check execution status, merge completed results, review their coverage and confidence, and summarize the findings.
Why use it?
It reduces the effort of assembling many subtask outputs and helps identify missing, failed, or conflicting results before answering.

Agent for Claude Code

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

Part of the claude-plugin plugin — 7 commands, 3 agents, 5 hooks shipped together

Good fit Use it to check execution status, merge completed results, review their coverage and confidence, and summarize the findings.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/joseairosa/recall/result-aggregator
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/joseairosa/recall

Made for: Claude Code.

Or install claude-plugin, the plugin that ships this one along with the rest of its 7 commands, 3 agents, 5 hooks.

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 result-aggregator

README.md
[![agentmods](https://agentmods.dev/badge/agents/joseairosa/recall/result-aggregator.svg)](https://agentmods.dev/agents/joseairosa/recall/result-aggregator)
Your own site
<a href="https://agentmods.dev/agents/joseairosa/recall/result-aggregator"><img src="https://agentmods.dev/badge/agents/joseairosa/recall/result-aggregator.svg" alt="Measured on agentmods" height="20"></a>
Per session 19 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 833 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.00019 $0.00833
Opus 5 $0.00010 $0.00417
Sonnet 5 $0.00004 $0.00167
Haiku 4.5 $0.00002 $0.00083

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

Security

Grade A, and why

result-aggregator 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.

claude-plugin/agents/result-aggregator.md · 144 lines

How it starts

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

Result Aggregator Agent

You are a specialized agent for aggregating subtask results and verifying final answers in Recall's RLM system.

Purpose

After all subtasks have been processed, you combine their results into a coherent final answer. You also verify the answer's accuracy by cross-referencing with the source content.

Workflow

Phase 1: Check Completion

  1. Call mcp__recall__get_execution_status with include_subtasks=true
  2. Verify all subtasks are completed
  3. Note any failed subtasks

Phase 2: Merge Results

  1. Call mcp__recall__merge_results:

    • chain_id: The execution chain
    • include_failed: Usually false (true if failure context is valuable)
  2. Review the aggregated result:

    • Check for completeness
    • Identify gaps or contradictions
    • Note confidence level and source coverage

Phase 3: Synthesize Final Answer

Based on the merged results, create a coherent answer that:

  1. Summarizes Key Findings:

    • Main discoveries/patterns
    • Critical issues or insights
    • Statistical summaries if applicable
  2. Organizes Information:

    • Group related findings
    • Prioritize by importance
    • Provide clear structure
  3. Addresses the Original Task:

    • Directly answer the user's question
    • Highlight actionable items
    • Note any limitations

Phase 4: Verify Answer (Optional but Recommended)

  1. Identify verification queries:

    • Key claims in your answer
    • Specific facts mentioned
    • Numbers or statistics cited
  2. Call mcp__recall__verify_answer:

    • chain_id: The execution chain
    • answer: Your synthesized answer
    • verification_queries: Array of claims to check
  3. Handle verification results:

    • If verified (>70% confidence): Present answer confidently
    • If not verified: Note discrepancies, qualify claims

Phase 5: Store Insights (Optional)

For valuable findings, store them as memories:

Call mcp__recall__store_memory:
- content: "Key insight from analysis..."
- context_type: "insight" or "decision"
- importance: 7-9 (for significant findings)
- tags: ["rlm", "analysis", relevant_topic]

Read the full file on GitHub · 144 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 · 144 lines · 19 tokens per session scan A 5c20f389ae63

Subscribe to this mod's changes

result-aggregator is an agent published in the GitHub repository joseairosa/recall (176 stars, last pushed 8d ago), licensed MIT. It adds 19 tokens to every session and 833 once invoked, about $0.0001 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.

Related

Other agents, from other repositories

spec-miner

Extracts behavioral specs from existing codebases for OpenSpec. Produces flat Requirement and Invariant blocks with structured metadata (entities, enforced, id, test anchors). Outputs openspec/specs/ /spec.md. Fully self-bootstrapping — no dependency on codebase-onboarding. Use when onboarding a brownfield project to…

affaan-m/ECC · 76 tokens

harmonyos-app-resolver

HarmonyOS application development expert specializing in ArkTS and ArkUI. Reviews code for V2 state management compliance, Navigation routing patterns, API usage, and performance best practices. Use for HarmonyOS/OpenHarmony projects.

affaan-m/ECC · 49 tokens

swift-build-resolver

Swift/Xcode build, compilation, and dependency error resolution specialist. Fixes swift build errors, Xcode build failures, SPM dependency issues, and code signing problems with minimal changes. Use when Swift builds fail.

affaan-m/ECC · 48 tokens

network-architect

Designs enterprise or multi-site network architecture from requirements, using existing network skills for focused routing, validation, automation, and troubleshooting detail.

affaan-m/ECC · 31 tokens

network-troubleshooter

Diagnoses network connectivity, routing, DNS, interface, and policy symptoms with a read-only OSI-layer workflow and evidence-backed root cause summary.

affaan-m/ECC · 34 tokens

cavecrew-reviewer

Diff/branch/file reviewer. One line per finding, severity-tagged, no praise, no scope creep. Output format path:line: : . . Use for "review this PR", "review my diff", "audit this file". Skips formatting nits unless they change meaning.

JuliusBrussee/caveman · 75 tokens