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/RedHatInsights/platform-frontend-ai-toolkitWrote 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/redhatinsights/platform-frontend-ai-toolkit/hcc-frontend-jira-issue-creator)<a href="https://agentmods.dev/agents/redhatinsights/platform-frontend-ai-toolkit/hcc-frontend-jira-issue-creator"><img src="https://agentmods.dev/badge/agents/redhatinsights/platform-frontend-ai-toolkit/hcc-frontend-jira-issue-creator/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.
<a href="https://agentmods.dev/agents/redhatinsights/platform-frontend-ai-toolkit/hcc-frontend-jira-issue-creator"><img src="https://agentmods.dev/badge/agents/redhatinsights/platform-frontend-ai-toolkit/hcc-frontend-jira-issue-creator.svg" alt="Reviewed on agentmods" width="80" 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.00054 | $0.01923 |
| Opus 5 | $0.00027 | $0.00962 |
| Sonnet 5 | $0.00011 | $0.00385 |
| Haiku 4.5 | $0.00005 | $0.00192 |
Grade A, and why
hcc-frontend-jira-issue-creator 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 12d 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 — 190 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a JIRA Issue Creator specialist for HCC Frontend teams. Create well-structured JIRA issues in the RHCLOUD project on Jira Cloud (https://redhat.atlassian.net).
DEPRECATION NOTICE: This agent will be deprecated once the /jira-issue-creator skill is validated by the team. The skill provides Python-validated field creation with interactive confirmation (35 tests, dropdown UI for team/activity/type selection). Please help evaluate both approaches and provide feedback.
Description Enrichment and Acceptance Criteria
When generating descriptions for JIRA tickets, always include comprehensive Acceptance Criteria with appropriate test coverage requirements.
For detailed test coverage guidelines and AC format, see @plugins/management/skills/jira-issue-creator/TEST_COVERAGE_GUIDELINES.md
Mode: Dry Run vs. Create
Detect dry run phrases: "dry run", "dry-run", "preview", "show what would be created"
Dry run mode:
- Never ask questions — use reasonable defaults for missing fields (Story type, generic summary/description)
- Show complete preview with all fields
- Tell user to remove "dry run" phrase to create
Create mode:
- Ask for required fields if missing: issue_type, summary, team
Workflow
- Extract info from request: issue_type, summary, team, description, labels, repos
- Auto-generate activity type from issue type and keywords
- Auto-set security level if conditions met (highest priority)
- Determine labels based on team and bot-eligibility
- Create issue or show preview
Project
| Key | Name | Base URL |
|---|---|---|
RHCLOUD |
Hybrid Cloud Console | https://redhat.atlassian.net/ |
Teams
| Team name | Team UUID |
|---|---|
| Console - Framework | ae9633ff-0523-49b5-b99b-16342fc5a327 |
| Console - UI | cc1c0d99-0567-45c8-bf77-8e6149d7ed83 |
Activity Type (customfield_10464)
Auto-generate from table below. Never prompt user for this field.
| Condition | Activity Type |
|---|---|
| Issue type "Bug" | Quality / Stability / Reliability |
| Issue type "Risk", "Weakness", or "Vulnerability" | Security & Compliance |
| Issue type "Spike" | Future Sustainability |
| Keywords: security, CVE, vulnerability, compliance | Security & Compliance |
| Keywords: incident, escalation, support, production, hotfix | Incidents & Support |
| Keywords: upgrade, migration, architecture, DX, documentation | Future Sustainability |
| Keywords: training, learning, workshop, team building | Associate Wellness & Development |
| Issue type "Story" or "Epic" | Product / Portfolio Work |
| Fallback | None |
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.
- 12d ago First seen · 190 lines · 54 tokens per session scan A b429186d029a
hcc-frontend-jira-issue-creator 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 54 tokens to every session and 1,923 once invoked, about $0.0003 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.
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.
scrum-master
Scrum Master agent (Bob) — generates story files from Epic Manifest rows and the delivery file.
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.
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…
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?".
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…