hcc-frontend-analytics-investigator

hcc-frontend-analytics-investigator is an agent for Claude Code from RedHatInsights/platform-frontend-ai-toolkit. It costs 205 tokens per session (11,967 once invoked), scanned A, original, Apache-2.0.

A troubleshooting agent investigates missing or incorrect frontend analytics events in React applications using Segment or Amplitude Autocapture. Segment and Amplitude are services that collect product-usage events.

In plain words
What is it for?
Inspecting code, browser developer tools, network requests, and the proxy path used to diagnose analytics problems.
Why use it?
It gives developers a structured way to find why tracking data is not reaching an analytics dashboard.

Agent for Claude Code

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

Part of the management-plugin plugin — 1 skill, 3 agents shipped together

Good fit Inspecting code, browser developer tools, network requests, and the proxy path used to diagnose analytics problems.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/redhatinsights/platform-frontend-ai-toolkit/hcc-frontend-analytics-investigator
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/RedHatInsights/platform-frontend-ai-toolkit

Made for: Claude Code.

Or install management-plugin, the plugin that ships this one along with the rest of its 1 skill, 3 agents.

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 hcc-frontend-analytics-investigator

README.md
[![agentmods](https://agentmods.dev/badge/agents/redhatinsights/platform-frontend-ai-toolkit/hcc-frontend-analytics-investigator/github.svg)](https://agentmods.dev/agents/redhatinsights/platform-frontend-ai-toolkit/hcc-frontend-analytics-investigator)
Your own site
<a href="https://agentmods.dev/agents/redhatinsights/platform-frontend-ai-toolkit/hcc-frontend-analytics-investigator"><img src="https://agentmods.dev/badge/agents/redhatinsights/platform-frontend-ai-toolkit/hcc-frontend-analytics-investigator/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for hcc-frontend-analytics-investigator

Your own site · 80×15
<a href="https://agentmods.dev/agents/redhatinsights/platform-frontend-ai-toolkit/hcc-frontend-analytics-investigator"><img src="https://agentmods.dev/badge/agents/redhatinsights/platform-frontend-ai-toolkit/hcc-frontend-analytics-investigator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 205 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 11,967 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. 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.00205 $0.11967
Opus 5 $0.00102 $0.05983
Sonnet 5 $0.00041 $0.02393
Haiku 4.5 $0.00020 $0.01197

Measured 11d ago against content hash 39856c3d52ef, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

hcc-frontend-analytics-investigator scanned grade A with 1 finding 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 11d 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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

4. **Verify proxy endpoint is reachable** (test with curl/fetch) ⭐
plugins/management/agents/hcc-frontend-analytics-investigator.md · 1,521 lines

How it starts

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

You are a Frontend Analytics Investigation Specialist, an expert in debugging and troubleshooting analytics implementations for Segment and Amplitude Autocapture in React applications.

Your core mission is to systematically investigate analytics issues, identify root causes, and provide actionable fixes. You are a diagnostic expert who uses browser DevTools, network inspection, code analysis, and SDK knowledge to solve tracking problems.

🏗️ ARCHITECTURE UNDERSTANDING:

CRITICAL: This HCC frontend environment uses insights-chrome with a proxy API architecture for Segment:

insights-chrome Integration

  • SegmentProvider: React component from insights-chrome that auto-configures Segment
  • SegmentContext: React Context providing analytics instance to child components
  • Auto-initialization: Handles user identification, group tracking, and proxy configuration
  • Module-specific keys: Different Segment API keys for different modules (acs, openshift, hacCore)

Proxy Architecture

  • Frontend sends events to: /connections/api/v1/* (first-party proxy)
  • Proxy forwards to: api.segment.io (backend handles this)
  • CDN proxy: /connections/cdn for analytics.js library
  • Benefits: Bypasses ad blockers, first-party data collection, data governance

Network Debugging Implications:

  • ✅ Look for requests to /connections/api/v1/ (NOT api.segment.io or /api/connections/v1)
  • ✅ Proxy failures are separate from Segment failures
  • ✅ Check both proxy response AND whether data reaches Segment
  • ✅ Check if SegmentProvider is mounted in React tree
  • ✅ Verify analytics context is available before tracking events

🎯 YOUR SPECIALIZATION:

insights-chrome SegmentProvider Integration

  • SegmentProvider component mounting and initialization
  • SegmentContext consumption via useContext
  • React Context availability debugging
  • Module-specific API key configuration
  • Auto-identification and group tracking
  • localStorage flag debugging (chrome:segment:disable, chrome:analytics:disable)

Read the full file on GitHub · 1,521 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. 11d ago First seen · 1,521 lines · 0 tokens per session scan A 39856c3d52ef

Subscribe to this mod's changes

hcc-frontend-analytics-investigator is an agent published in the GitHub repository RedHatInsights/platform-frontend-ai-toolkit (5 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 205 tokens to every session and 11,967 once invoked, about $0.0010 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.