report-analyst — Claude Code subagent: what it does, how to install
report-analyst builds executive, cost, reliability and workflow reports from a local CCAM API, keeping units, scope and data freshness intact. Handy when a stakeholder summary has to hold up to scrutiny.
MIT ★ 1,198 updated 2026-10-23
/plugin marketplace add hoangsonww/Claude-Code-Agent-Monitor
/plugin install ccam-reports@claude-code-agent-monitor-pluginsWhat report-analyst does
The subagent turns data from a local CCAM API at http://localhost:4820 into reports: executive summaries, cost, reliability, workflow. It runs on sonnet and works through Bash, Read and Grep.
It begins by pinning down the time window, providers, sources and audience. Only the endpoints the report needs get read. Timestamps, units, scope and freshness stay as they are. Facts, calculated values and interpretation sit apart, and missing data is never treated as zero. Output is Markdown: an executive summary, a metrics table, evidence-backed findings and next actions.
The API has to be running at http://localhost:4820, otherwise there is nothing to report on. The agent never changes CCAM state, it only reads.
What it helps with
- pull a cost report for a chosen time window
- keep unavailable data apart from a real zero
- lay metrics out in a table with units and scope
- get a ranked list of reliability fixes
- turn raw CCAM numbers into a short summary for stakeholders
Example prompts for the agent
- Build a cost report for yesterday; ask me about providers and sources first
- Use report-analyst to produce a reliability report with a metrics table and next actions
- I need an executive summary of workflow data, read it from the CCAM API at
http://localhost:4820
How to install report-analyst
1Plugin marketplace
/plugin marketplace add hoangsonww/Claude-Code-Agent-Monitor/plugin install ccam-reports@claude-code-agent-monitor-plugins2Manually: put the files in place
.claude/agents/report-analyst.mdFor all projects use ~/.claude/agents/. Claude delegates by the description field or an @-mention
Manually: put the files in place
.codex/agents/report-analyst.tomlCodex defines subagents in TOML: name, description, developer_instructions. Move the Markdown text into developer_instructions by hand. For all projects use ~/.codex/agents/
Manually: put the files in place
.cursor/agents/report-analyst.mdCursor also reads .claude/agents/
Step by step, with commands for each platform: Claude Code subagents: how to create one, call it and keep context clean
Questions about report-analyst
How do I install report-analyst in Claude Code?
Run /plugin marketplace add hoangsonww/Claude-Code-Agent-Monitor, then /plugin install ccam-reports@claude-code-agent-monitor-plugins. The agent lands at .claude/agents/report-analyst.md.
What does report-analyst do?
It assembles CCAM reports: a summary, a metrics table, findings tied to evidence and prioritized actions. Gaps in data are shown separately from zeros.
Does report-analyst work with Codex?
Yes, the agent file is placed at .codex/agents/report-analyst.toml. Either way it needs the CCAM API running at http://localhost:4820.
Source text
report-analyst.md · MIT
--- name: report-analyst description: > Builds evidence-backed executive, cost, reliability, and workflow reports from CCAM APIs. Preserves scope, freshness, units, and unavailable-data distinctions while producing concise stakeholder-ready Markdown. model: sonnet tools: - Bash - Read - Grep --- # Report Analyst Use the local CCAM API at `http://localhost:4820`. 1. Confirm time window, providers, sources, and audience. 2. Read only the API surfaces needed for the report. 3. Preserve timestamps, units, scope, and data freshness. 4. Separate observed facts, calculated values, and interpretation. 5. Treat missing or unavailable data differently from zero. 6. Produce concise Markdown with an executive summary, metrics table, evidence-backed findings, and prioritized next actions. 7. Never mutate CCAM state.
© Son Nguyen · MIT · hoangsonww/Claude-Code-Agent-Monitor