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/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/rules/openshift/hypershift/debug-aro-hcp-e2e)<a href="https://agentmods.dev/rules/openshift/hypershift/debug-aro-hcp-e2e"><img src="https://agentmods.dev/badge/rules/openshift/hypershift/debug-aro-hcp-e2e/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/rules/openshift/hypershift/debug-aro-hcp-e2e"><img src="https://agentmods.dev/badge/rules/openshift/hypershift/debug-aro-hcp-e2e.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.00017 | $0.01703 |
| Opus 5.5 | $0.00007 | $0.00681 |
| Sonnet 5.5 | $0.00003 | $0.00341 |
| Haiku 4.5 | $0.00002 | $0.00170 |
Grade A, and why
debug-aro-hcp-e2e 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 1mo 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 — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Debugging ARO HCP e2e Tests
Use this rule when a PR or CI job for ARO HCP (Azure) e2e tests fails. It points to where to look in artifacts, and prescribes fast triage workflows. See also: docs/content/reference/test-information-debugging/Azure/test-artifacts-directory-structure.md
Quick links to artifacts
- Hosted control plane components
- Control plane pod deployments:
artifacts/e2e-aks/hypershift-azure-run-e2e/artifacts/Test*/namespaces/e2e-clusters-*/apps/deployments/ - Control plane pod manifests:
artifacts/e2e-aks/hypershift-azure-run-e2e/artifacts/Test*/namespaces/e2e-clusters-*/core/pods/ - Control plane pod logs:
artifacts/e2e-aks/hypershift-azure-run-e2e/artifacts/Test*/namespaces/e2e-clusters-*/core/pods/logs/
- Control plane pod deployments:
- HyperShift management cluster (namespace
hypershift/)- Operator deployment:
.../namespaces/hypershift/apps/deployments/operator.yaml - External DNS deployment:
.../namespaces/hypershift/apps/deployments/external-dns.yaml - Operator logs:
.../namespaces/hypershift/core/pods/logs/operator-*-operator.log - External DNS logs:
.../namespaces/hypershift/core/pods/logs/external-dns-*-external-dns.log
- Operator deployment:
- Primary test directory:
artifacts/e2e-aks/hypershift-azure-run-e2e/ - Top-level CI files
- Build log:
artifacts/build-log.txt - CI operator log:
artifacts/ci-operator-*/ci-operator.log - JUnit:
artifacts/e2e-aks/hypershift-azure-run-e2e/artifacts/junit.xml - Job result:
finished.json
- Build log:
Start here: critical HyperShift resources
Check the status of these first; their .status often names the failing subsystem:
- HostedCluster:
.../namespaces/e2e-clusters-*/hypershift.openshift.io/hostedclusters/*.yaml - HostedControlPlane:
.../namespaces/e2e-clusters-*-{test-name}-*/hypershift.openshift.io/hostedcontrolplanes/*.yaml - NodePool:
.../namespaces/e2e-clusters-*/hypershift.openshift.io/nodepools/*.yaml
Expect to see:
- Overall readiness conditions
- Infra provisioning state
- Control plane component health
- NodePool scaling/readiness
- Failure reasons/messages
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.
- 1mo ago First seen · 128 lines · 17 tokens per session scan A 86fc95c20511
debug-aro-hcp-e2e is a cursor rule published in the GitHub repository openshift/hypershift (547 stars, last pushed today), licensed Apache-2.0. It adds 17 tokens to every session and 1,703 once invoked, about $0.0001 per session on Opus 5.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 cursor rules, from other repositories
running-tests
How to run tests, check for failures, and rerun specific failing tests — use the :agent variants of slow commands.
playwright-defect-tracking-cursorrules-prompt-file
Cursor rules for Playwright development with defect tracking.
turn-admission
Immediate turn admission and autonomous retry semantics.
nodebench-auto-qa
Auto-QA after code changes using NodeBench MCP tools.
fusebase-flow-validation
Fusebase Flow validation/verification phase rules. Use when running gate checks, reviewing diffs, or verifying smoke prompts.
playwright-defect-tracking-cursorrules-prompt-file
Cursor rule "playwright-defect-tracking-cursorrules-prompt-file" from XD3an/awesome-ai-coding-all-in-one, covering persona, auto-detect typescript usage, defect tracking focus, best practices and configuration example.