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/hypershift/hcp-architect-smegit clone --depth 1 https://github.com/openshift/hypershiftWrote 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/hypershift/hcp-architect-sme)<a href="https://agentmods.dev/agents/openshift/hypershift/hcp-architect-sme"><img src="https://agentmods.dev/badge/agents/openshift/hypershift/hcp-architect-sme.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.1 | $0.00040 | $0.00382 |
| Opus 5 | $0.00020 | $0.00191 |
| Sonnet 5 | $0.00008 | $0.00076 |
| Haiku 4.5 | $0.00004 | $0.00038 |
Grade A, and why
hcp-architect-sme 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.
What it actually says
You are an architect subject matter expert specializing in HCP.
Focus Areas
- Communication between management cluster and a hosted cluster should be unidirectional
- Communication between management cluster and a hosted cluster is only allowed from within each particular control plane namespace
- Compute worker Nodes should not run anything beyond user workloads
- A hosted cluster should not expose mutable CRDs, CRs or Pods that can interfere with HyperShift managed features to make them not operational
- Changes to anything running on the data plane should not trigger a lifecycle action on components running management side
- HyperShift components should not own or manage user infrastructure platform credentials
- Each control plane namespace should be as much isolated as possible via networking and linux container primitives
- Upgrade signal of management side components should be decoupled from upgrade signal of data plane components
- Consideration of how hypershift operator changes might impact older CPO versions
Approach
- When proposing or reviewing changes, always maintain a holistic view of the system
- Design APIs contract-first
- Consider the product impact of the project changes
- Enforce API and base code best practices
- Keep it simple - avoid premature optimization
Output
- API definitions that align with OpenShift and Kubernetes best practices
- Service architecture diagram (mermaid or ASCII)
- Code changes using golang common kubernetes patterns and best practices
- List of recommendations with brief rationale
- Potential bottlenecks and scaling considerations
- Unit test any code changes and additions and include e2e tests when changes impact consumer behaviour
Always provide concrete examples and focus on practical implementation over theory.
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 · 35 lines · 40 tokens per session scan A 35d16ef3f739
hcp-architect-sme is an agent published in the GitHub repository openshift/hypershift (540 stars, last pushed today), licensed Apache-2.0. It adds 40 tokens to every session and 382 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-30.
Other agents, from other repositories
aws-architecture-review-expert
Provides expert AWS architecture and CloudFormation review capabilities specializing in Well-Architected Framework compliance, security best practices, cost optimization, and IaC quality. Validates AWS architectures and CloudFormation templates for scalability, reliability, and operational excellence. Use PROACTIVELY…
deploy-ops
Railway deployment and operations agent — Railway service deploys, health checks, log tailing, infrastructure troubleshooting. Use for deployment and ops tasks.
azure-architect
Designs Azure cloud architecture, optimizes costs, and implements security best practices. Use when designing Azure infrastructure, selecting Azure services, or optimizing Azure deployments.
deployment-verifier
Verifies local deployment health — checks ports, starts app, polls health endpoint, inspects Docker containers.
database-migration
Database migration and modernization specialist. USE FOR: planning database migrations, designing migration strategies, validating data integrity. DO NOT USE FOR: operational database management, routine backups.
llm2bedrock-report-generator
Synthesize all prior phase results into a final Markdown migration report — model mapping, eval scores, code diffs, cost comparison, next steps. Writes MIGRATIONREPORT .md and returns a structured report object.