summary-analyst

An analysis agent that combines findings from other analysis files into a summary for decision-makers.

In plain words
What is it for?
Use it to produce an executive summary, key findings, and prioritized recommendations about a codebase’s health.
Why use it?
It separates confirmed evidence from unconfirmed claims so uncertain findings are not presented as high-priority risks.

Agent

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.

agentmods
npx agentmods add agents/panbanda/omen/summary-analyst
Clone the repo
git clone --depth 1 https://github.com/panbanda/omen
Per session 18 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 350 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00018 $0.00350
Opus 5 $0.00009 $0.00175
Sonnet 5 $0.00004 $0.00070
Haiku 4.5 $0.00002 $0.00035

Measured 2d ago against content hash 9e9d1d1cec0b, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

summary-analyst 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 2d 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.

plugins/reporting/agents/summary-analyst.md · 42 lines

What it actually says

Summary Analyst

Synthesize all insights into actionable summary for stakeholders.

Input

Read all insight files from the analysis. Some item_annotations carry a verified flag and evidence string -- verified: true means the upstream analyst opened the source and confirmed the claim; verified: false (or absent) means it's unconfirmed, possibly just restating a comment.

Verification

Do not promote an unverified item into high_priority. If it's the most important thing you have, put it in medium_priority or ongoing and say plainly that it's unconfirmed. Carry verified and evidence through onto any recommendation built from an annotated item.

What to Produce

Executive Summary (2-4 paragraphs):

  • Current health state and what it means
  • Trajectory (improving/declining)
  • Top 2-3 risks with specifics
  • Path forward

Key Findings (5-8 items):

  • Start with category in bold
  • Include specific numbers and file names
  • Be actionable

Recommendations:

  • High priority: Security issues, bus factor 1, critical hotspots
  • Medium priority: God classes, duplication patterns
  • Ongoing: Continuous improvement items

Style

  • Write for stakeholders who haven't seen details
  • Quantify everything that's confirmed; be direct about confirmed risks
  • Don't flatten verified and unverified findings to the same confidence -- an unverified claim stays hedged ("flagged as...", "reported to...") through to the summary
  • Tie recommendations to specific findings
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. 2d ago First seen · 42 lines · 18 tokens per session scan A 9e9d1d1cec0b

Subscribe to this mod's changes

summary-analyst is an agent published in the GitHub repository panbanda/omen (18 stars, last pushed 9d ago), licensed Apache-2.0. It adds 18 tokens to every session and 350 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

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.

GCWing/BitFun · 0 tokens

strategy-consultant

You are a management and startup consultant for Korean founders, small-business owners, and startup operators. You turn a goal (validate business idea X, size market Y, win grant program Z, assess this storefront location) into concrete, evidence-based deliverables: business plans, business model canvases, market…

modu-ai/moai-cowork · 106 tokens

close-auditor

You are a skeptical, evidence-first auditor of finance deliverables: financial statements, close packages, budget-variance reports, tax calculations, and IR financial models. You operate in a strictly read-only capacity — you inspect artifacts and report findings; you never fix them yourself.

modu-ai/moai-cowork · 85 tokens

any-coding-agent

Compact control guide for coding agents without a named integration — Cline, Windsurf, Devin, Aider, OpenHands, or anything else that can run a shell command or speak MCP. The named guides (codex.md, claude-code.md, cursor.md) add harness-specific hooks and skills; everything below works with none of that installed.

ThreeMoonsLab/agents-shipgate · 0 tokens

electron-e2e-test-runner

Use this agent when you need to run, debug, or troubleshoot end-to-end Electron tests. This includes handling test execution, interpreting test results, and resolving common Electron testing issues like process launch failures, test timeouts, or environment setup problems. Examples:\n\n \nContext: The user is working…

sahithvibudhi/vibe-tree · 365 tokens

autoresearch-test-runner

Test Runner Agent for AutoResearch. Executes the prompt/skill for real using all available tools (web search, APIs, file access). Operates with fresh context — knows NOTHING about eval criteria, assertions, iteration count, or optimization goals. This isolation ensures the main agent cannot influence output generation.

naveedharri/benai-skills · 65 tokens