Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/wangke19/gemini-ai-helpersnpx agentmods add commands/wangke19/gemini-ai-helpers/list-componentsWrote 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/commands/wangke19/gemini-ai-helpers/list-components)<a href="https://agentmods.dev/commands/wangke19/gemini-ai-helpers/list-components"><img src="https://agentmods.dev/badge/commands/wangke19/gemini-ai-helpers/list-components/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/commands/wangke19/gemini-ai-helpers/list-components"><img src="https://agentmods.dev/badge/commands/wangke19/gemini-ai-helpers/list-components.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.00012 | $0.00647 |
| Opus 5 | $0.00006 | $0.00324 |
| Sonnet 5 | $0.00002 | $0.00129 |
| Haiku 4.5 | $0.00001 | $0.00065 |
Grade A, and why
list-components 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 9d 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 — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Name
teams:list-components
Synopsis
/teams:list-components [--team <team-name>]
Description
The teams:list-components command displays all OCPBUGS component names, with optional filtering by team.
This command is useful for:
- Discovering available OCPBUGS components
- Discovering OCPBUGS components for a specific team
- Validating OCPBUGS component names before filing or querying bugs
- Understanding which components are tracked in OCPBUGS per team
- Finding exact component names for use in JIRA queries
Implementation
-
Verify Working Directory
- Ensure you are in the repository root directory
- Run
pwdto confirm
-
Run the list-components Script
- For all components:
python3 extensions/teams/skills/list-components/list_components.py - For team components:
python3 extensions/teams/skills/list-components/list_components.py --team "API Server" - Team names must match exactly (case-sensitive)
- For all components:
-
Parse and Display Results
- Script outputs JSON with total_components, components array, and optional team field
Examples
-
List all OCPBUGS components:
/teams:list-components -
List OCPBUGS components for a specific team:
/teams:list-components --team "API Server"
Arguments
--team(optional): Filter components by team name- Use
/teams:list-teamsto get available team names - Example:
--team "API Server"
- Use
Prerequisites
- Python 3.6 or later
Notes
- Only OCPBUGS components are returned
- Team names are case-sensitive - use
/teams:list-teamsto get correct names - Typical count: ~87 total components across 29 teams
- Reads from committed mapping file (no download needed)
Data Source
The team and component mapping data originates from:
- Source: https://gitlab.cee.redhat.com/hybrid-platforms/org
- Access: Requires Red Hat VPN connection
- Privacy: The full org data is considered somewhat private, so this project extracts only the team and component mapping
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.
- 9d ago First seen · 92 lines · 12 tokens per session scan A 0350de93c869
list-components is a command published in the GitHub repository wangke19/gemini-ai-helpers (2 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 12 tokens to every session and 647 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-09-03.
Other commands, from other repositories
projects
Provides tools for creating and managing your Supabase projects.
session-list
List recent sessions from the project ledger and offer to view one.
7a_stakeholder_comms
Generate stakeholder-facing communications: release notes, demo scripts, and change briefs.
convert-to-plan
Convert planning artifacts (lite-plan, workflow session, markdown) to issue solutions.
execute
Execute queue with DAG-based parallel orchestration (one commit per solution).
queue
Form execution queue from bound solutions using issue-queue-agent (solution-level).