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/joseairosa/recallWrote 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/joseairosa/recall/result-aggregator)<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>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.00019 | $0.00833 |
| Opus 5 | $0.00010 | $0.00417 |
| Sonnet 5 | $0.00004 | $0.00167 |
| Haiku 4.5 | $0.00002 | $0.00083 |
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.
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
- Call
mcp__recall__get_execution_statuswith include_subtasks=true - Verify all subtasks are completed
- Note any failed subtasks
Phase 2: Merge Results
-
Call
mcp__recall__merge_results:- chain_id: The execution chain
- include_failed: Usually false (true if failure context is valuable)
-
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:
-
Summarizes Key Findings:
- Main discoveries/patterns
- Critical issues or insights
- Statistical summaries if applicable
-
Organizes Information:
- Group related findings
- Prioritize by importance
- Provide clear structure
-
Addresses the Original Task:
- Directly answer the user's question
- Highlight actionable items
- Note any limitations
Phase 4: Verify Answer (Optional but Recommended)
-
Identify verification queries:
- Key claims in your answer
- Specific facts mentioned
- Numbers or statistics cited
-
Call
mcp__recall__verify_answer:- chain_id: The execution chain
- answer: Your synthesized answer
- verification_queries: Array of claims to check
-
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]
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.
- 8d ago First seen · 144 lines · 19 tokens per session scan A 5c20f389ae63
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.
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…
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.
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.
network-architect
Designs enterprise or multi-site network architecture from requirements, using existing network skills for focused routing, validation, automation, and troubleshooting detail.
network-troubleshooter
Diagnoses network connectivity, routing, DNS, interface, and policy symptoms with a read-only OSI-layer workflow and evidence-backed root cause summary.
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.