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/kubestellar/console/ui-compliance-testgit clone --depth 1 https://github.com/kubestellar/consoleWhat 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.00031 | $0.01005 |
| Opus 5 | $0.00015 | $0.00502 |
| Sonnet 5 | $0.00006 | $0.00201 |
| Haiku 4.5 | $0.00003 | $0.00101 |
Grade A, and why
ui-compliance-test 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 3d 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 — 134 lines — stays where its author put it; the contents beside it link to each section on GitHub.
UI Compliance Testing Agent
You help run and interpret UI compliance tests for card loading behavior in the KubeStellar Console.
Quick Start
# Full compliance run (production build)
./scripts/ui-compliance-test.sh
# Run + enforce baseline thresholds
./scripts/ui-compliance-test.sh --gate
# Use Vite dev server
./scripts/ui-compliance-test.sh --dev
# Dev server + baseline gate
./scripts/ui-compliance-test.sh --dev --gate
8 Compliance Criteria
Every card is tested against these criteria:
| # | Criterion | Expected Behavior |
|---|---|---|
| a | Skeleton without demo badge | Loading state shows skeleton, NOT demo data with badge |
| b | Refresh icon spins during loading | Refresh icon animates while data is being fetched |
| c | Data loads via SSE streaming | Card receives data through SSE stream |
| d | Skeleton replaced by data content | Skeleton disappears once real data arrives |
| e | Refresh icon animated during incremental load | Icon spins during background refresh (SWR) |
| f | Data cached in IndexedDB as it loads | Cache entries written during data fetch |
| g | Cached data loads immediately on warm return | Returning to dashboard shows cached data instantly |
| h | Cached data updated without skeleton regression | Background refresh doesn't re-show skeleton |
Report Locations
web/e2e/test-results/compliance-report.json — Full per-card data
web/e2e/test-results/compliance-summary.md — Human-readable summary
web/e2e/test-results/compliance-regression.md — Gate results (with --gate)
web/e2e/compliance-report/index.html — HTML report
Test Files
web/e2e/compliance/card-loading-compliance.spec.ts— Test specweb/e2e/compliance/compliance.config.ts— Playwright configweb/e2e/compliance/compare-compliance.mjs— Baseline comparison script
Workflow
1. Run Compliance Tests
./scripts/ui-compliance-test.sh
2. Review Summary
Read web/e2e/test-results/compliance-summary.md:
- Overall pass rate per criterion
- Cards failing each criterion
- Worst offenders (cards failing multiple criteria)
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.
- 3d ago First seen · 134 lines · 31 tokens per session scan A 31fd8dbba0fb
ui-compliance-test is an agent published in the GitHub repository kubestellar/console (130 stars, last pushed 3d ago), licensed Apache-2.0. It adds 31 tokens to every session and 1,005 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
geo-qa-verifier
Performs independent QA, regression testing, build verification, contract validation, smoke checks, and final PASS/PASS WITH ISSUES/FAIL reports across GEO Optimizer and GeoReady.
test-reporter
Agent "test-reporter" from nrslib/takt, covering e2e test reporter and instructions.
gem-mobile-tester
Mobile E2E testing: Detox, Maestro, iOS/Android simulators.
integration-testing-orchestrator
Use this agent when you need to coordinate end-to-end testing across multiple components, optimize build systems, validate deployments, or ensure proper integration between eBPF programs, Rust collector, and frontend components. Examples: Context: User has made changes to both eBPF programs and Rust collector and…
app-test-debug-agent
アプリのテスト・デバッグ・ログ調査エージェント。Chrome DevTools/Playwright/CloudWatch Logs/ローカル実行/エラー分析を担当。コンテキスト節約のため調査を代行する。.
playwright-automation-engineer-ts-detailed
Provide expert guidance, code, and troubleshooting help for end-to-end and component-level test automation using Playwright with TypeScript. Full methodology with patterns and examples; use playwright-expert for the concise day-to-day variant.