hcc-frontend-weekly-report

hcc-frontend-weekly-report is an agent for Claude Code from RedHatInsights/platform-frontend-ai-toolkit. It costs 32 tokens per session (2,444 once invoked), scanned A, original, Apache-2.0.

A weekly report generator that reviews Jira issues and groups completed team work into standard report sections. Jira is a system for tracking software tasks and their status.

In plain words
What is it for?
Use it to report work identified by Jira components, labels, assignees, projects, or combinations of those criteria.
Why use it?
It limits the report to specified teams and completed issue statuses, reducing manual searching and inconsistent weekly summaries.

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 Use it to report work identified by Jira components, labels, assignees, projects, or combinations of those criteria.

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

README.md
[![agentmods](https://agentmods.dev/badge/agents/redhatinsights/platform-frontend-ai-toolkit/hcc-frontend-weekly-report/github.svg)](https://agentmods.dev/agents/redhatinsights/platform-frontend-ai-toolkit/hcc-frontend-weekly-report)
Your own site
<a href="https://agentmods.dev/agents/redhatinsights/platform-frontend-ai-toolkit/hcc-frontend-weekly-report"><img src="https://agentmods.dev/badge/agents/redhatinsights/platform-frontend-ai-toolkit/hcc-frontend-weekly-report/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-weekly-report

Your own site · 80×15
<a href="https://agentmods.dev/agents/redhatinsights/platform-frontend-ai-toolkit/hcc-frontend-weekly-report"><img src="https://agentmods.dev/badge/agents/redhatinsights/platform-frontend-ai-toolkit/hcc-frontend-weekly-report.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 32 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,444 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.00032 $0.02444
Opus 5 $0.00016 $0.01222
Sonnet 5 $0.00006 $0.00489
Haiku 4.5 $0.00003 $0.00244

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

Security

Grade A, and why

hcc-frontend-weekly-report 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 10d 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/management/agents/hcc-frontend-weekly-report.md · 282 lines

How it starts

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

You are an expert at analyzing JIRA issues and generating comprehensive weekly team reports. Your role is to query JIRA, analyze completed work, and organize findings into a structured weekly report format.

Team Identification

The user will provide team identification criteria when requesting a report. Teams are typically identified by:

  • Component: Component name(s) in JIRA
  • Label: Label(s) associated with the team
  • Assignee: Specific team members
  • Project: JIRA project key(s)
  • Custom criteria: Any combination of the above

Example team identifications:

  • Platform Framework: component="Console Framework" OR labels=platform-experience-services
  • Platform UI: component="Console UI" OR labels=platform-experience-ui
  • Experience Services: component="Console Framework" OR labels=platform-experience-services

Report Scope

IMPORTANT: Only include issues with status:

  • "Release pending"
  • "Closed"

This ensures the report reflects completed work from the week.

JQL Query Strategy

Weekly reports always look back to the most recent Wednesday (inclusive). Calculate the number of days to look back based on the current day of the week:

  • Wednesday: 0 days back (updated >= 0d)
  • Thursday: 1 day back (updated >= -1d)
  • Friday: 2 days back (updated >= -2d)
  • Saturday: 3 days back (updated >= -3d)
  • Sunday: 4 days back (updated >= -4d)
  • Monday: 5 days back (updated >= -5d)
  • Tuesday: 6 days back (updated >= -6d)

Query Template:

(<USER_PROVIDED_TEAM_CRITERIA>)
AND status IN ("Release pending", "Closed")
AND updated >= -Nd

Example query when run on Monday for Platform Framework team:

(component="Platform Framework" OR labels=platform-experience-services)
AND status IN ("Release pending", "Closed")
AND updated >= -5d

This ensures the report always covers from the most recent Wednesday through today, regardless of when it's run.

Report Template

Organize your findings into these sections:

Read the full file on GitHub · 282 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. 10d ago First seen · 282 lines · 32 tokens per session scan A f9eda7a3af1a

Subscribe to this mod's changes

hcc-frontend-weekly-report 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 32 tokens to every session and 2,444 once invoked, about $0.0002 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-31.

Related

Other agents, from other repositories

project-implementer

Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.

athola/claude-night-market · 38 tokens

scrum-master

Scrum Master agent (Bob) — generates story files from Epic Manifest rows and the delivery file.

LuisFelipeMoro/Harness-devkit · 24 tokens

onboard-guide

Onboarding assistant that provides ongoing personalized guidance after initial /onboard. Use for questions about conventions, architecture, patterns, or "where do I put this?" — answers are tailored to the engineer's background.

smicolon/ai-kit · 46 tokens

jira-analyst

Read full Jira ticket context (description, comments, attachments, links, media) and produce structured analysis suitable for posting back as a Jira comment. Read-only via the jira-as CLI wrapper. Routed by mk:jira-analyst skill. NOT for complexity scoring (jira-evaluator); NOT for story-point estimation…

ngocsangyem/MeowKit · 72 tokens

pm-advisor

You are pm-advisor — great-pm's external-perspective product advisor. You are NOT a process reviewer. You are the seasoned operator the founder pulls aside and says: "Be honest — what do you actually think of this?".

VandanaAjayDubey111/great-pm · 123 tokens

goals-onboarding

Use this agent to set up the OKR/goals system for a new company or project. Guides the user through defining annual objectives, key results, team quarterly OKRs, initiatives, tasks, support functions, and org chart. Generates YAML files following the workspace goals schema. Examples: Context: User wants to set up…

41fred/ace-level1 · 206 tokens