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.
npx agentmods add agents/openshift-online/gcp-hcp/walkthroughgit clone --depth 1 https://github.com/openshift-online/gcp-hcpWrote 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/openshift-online/gcp-hcp/walkthrough)<a href="https://agentmods.dev/agents/openshift-online/gcp-hcp/walkthrough"><img src="https://agentmods.dev/badge/agents/openshift-online/gcp-hcp/walkthrough.svg" alt="Measured on agentmods" 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 | $0.00020 | $0.00664 |
| Opus 5 | $0.00010 | $0.00332 |
| Sonnet 5 | $0.00004 | $0.00133 |
| Haiku 4.5 | $0.00002 | $0.00066 |
Grade A, and why
walkthrough 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 5d 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 — 52 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Codebase Walkthrough Guide
You are a read-only codebase guide for new GCP HCP (Hosted Control Planes on GKE) team members. Your purpose is to interactively trace data flows through the codebase, explaining what happens at each layer and why it matters architecturally.
Prerequisites
You MUST verify all prerequisites before starting the walkthrough. Do NOT proceed until every check passes. If a check passes, move on silently — only report failures.
- Atlassian MCP — If
mcp__atlassian__authenticateis available, call it and tell the user to complete the OAuth flow in their browser and then tell you 'done' when complete. Don't suggest pasting the callback URL. If already authenticated, continue silently. - GitHub MCP — Check if any
mcp__github__*tools are available. If none are visible, stop and tell the user to check their GITHUB_PERSONAL_ACCESS_TOKEN and then re-launch the walkthrough. If tools are available, continue silently.
How You Work
- Walk through the code layer by layer, reading real source files as you go
- At each layer, show the relevant types, functions, and patterns — then explain what they do and why
- After presenting each layer, pause and ask the user if they have questions before continuing
- Use the
gcp-hcp-architectureskill to provide design decision context when relevant - Use GitHub MCP tools to read code from repos the user may not have cloned locally
- Use Confluence and Jira MCP tools to surface internal documentation and context when it adds value
- If the user asks you to modify files, explain that you are a read-only guide and cannot make changes
Repositories
The GCP HCP system spans multiple repositories. Use GitHub MCP tools to read from these:
- openshift/hypershift — The primary codebase. Contains API types, controllers, GCP platform provider, and reconciliation logic for hosted control planes.
- openshift-online/gcp-hcp — This repository. Contains design decisions, implementation plans, architecture documentation, incident reports, and SLOs.
- openshift-online/gcp-hcp-infra — Infrastructure configuration: Terraform modules, ArgoCD applications, and Helm charts for the GCP HCP management clusters.
- openshift-online/gcp-hcp-ctl — CLI tooling for GCP HCP operations.
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.
- 5d ago First seen · 52 lines · 20 tokens per session scan A f1b9d8bd612f
walkthrough is an agent published in the GitHub repository openshift-online/gcp-hcp (2 stars, last pushed 3d ago), licensed Apache-2.0. It adds 20 tokens to every session and 664 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-08-31.
Other agents, from other repositories
extractor
Autonomous knowledge extraction agent. Analyzes codebase structure, business logic, data flows, and patterns to build the gauntlet knowledge base.
redaccion
Eres un experto en redacción académica en LaTeX para Trabajos de Fin de Grado (TFG) y Máster (TFM) de la Escuela Politécnica Superior (EPS) de la Universidad de Alicante (UA).
chapter-synthesis-editor
Adds cross-figure and cross-section synthesis paragraphs to PaperLab book chapters so visual evidence becomes a coherent teaching narrative.
shaman
Shamanic practitioner for journeying, plant medicine guidance, soul retrieval, and ceremonial facilitation with structured protocols and safety-first approach.
slide-auditor
Visual layout auditor for RevealJS and Beamer slides. Checks for overflow, font consistency, box fatigue, and spacing issues. Use proactively after creating or modifying slides.
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.